Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Weird Input/Output error in VFP3b
Message
From
09/07/1998 09:59:45
 
 
To
09/07/1998 09:52:50
Jerry Tovar
Dana Corporation Dana It
Maumee, Ohio, United States
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
00115668
Message ID:
00115687
Views:
14
>>>We have a few cases of "Input/Output Operation Failure" error message occuring in one of our VFP3b applications.
>>>
>>>In all cases, the PC is Win95. The error occurs when the user start the EXE.
>>>
>>>One of our users put a blank floppy in the A: drive and started the application and he said the error went away. However, without the floppy disk in, the error appears on startup.
>>>
>>>Our application does look for files on a CD-Rom, but not at the time that the error occurs and the app does not even look for a floppy.
>>>
>>>Any ideas,
>>>
>>>Jerryt
>>
>>It might be that some Form.DE still carries some hard-coded datapath from development machine.
>
>
>Edward,
>
>Thanks for the response.
>
>We have many different customers using this application for the past year. So far only 1 reported this problem.
>
>However, I am able to reproduce this problem on one of our laptops running a different VFP3b application. However this time, I placed a totally unrelated CD in the CD drive and the application works. Without a CD in the drive, I get a "Input/Output Operation Failure".
>
>In both applications, I run the EXE out of one directory and SET PATH TO a DATA directory in one app and a CD-Rom directory in another app.
>
>Again, the error only occurs on 2 PCs in the past year.
>
>Thanks,
>
>Jerryt

Again, it might be some specific mapping letter, e.g. maybe just these two machines have CD-ROM drive 'H:', and exactly this letter is hardcoded in some SCX file. Normally, if 'H:' is just hard/network drive it will not generate an error, because app just look there, cannot find something and proceed to SET PATH way. The 100% reliable way is to forget about SET PATH and reset DE.Cursor.Database properties programmatically.
Edward Pikman
Independent Consultant
Previous
Reply
Map
View

Click here to load this message in the networking platform