bonedoc

Ok, this will probably be vague, but I will give it a shot.

I have a database connection string that links me to my database. It all works great...but I found a bug. My app shows a dialog. In the dialog, you select a picture file, and it will save it in a set location. Later, I can view the pictures. Everything works...BUT, when I get a picture off a floppy disc, take the disc out....... the next time I try to pull up a picture, I get "Disk Error". It refers to the databasecommand.executereader() after the connection string. Apparently, the connection string somewhow changed after the picture was taken from the floppy. When I take it out and then use the app, it tries to access the floppy. Funny thing is the datapath on the file and the pic were saved in the correct location on my computer, so why would it even try this? Now, if I leave the disk in the entire time, it will work like normal...but it accesses the floppy everytime I view a picture. If anyone has the slightest idea as to why this may happen, please tell me. I can't figure this out. Thanks

wayneph

are you storing the picture in your database? or just a path to your picture?

my guess is that you are just storing the path to the picture, but when you take the floppy out it's no longer available. It shouldn't have anything to do with the connection string. you should only have problems when trying to view that single record.

bonedoc

I only store the path in the database and part of it in the registry. it gets the registry postion and adds it to the file name in the database. It has always worked fine, but I just noticed this little bug. Funny thing is that the registry nor the datapath say anything about the floppy drive, so I do not know why it would try to access it. You want to know something more odd, I just ran my app on another computer, and it did not have a single problem. I am confused...