Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Trapping LOCATE DB Error
Message
From
08/03/1999 11:41:05
Ian Matthews
Up & Running Technologies Inc
Chestermere, Alberta, Canada
 
 
To
25/02/1999 06:27:25
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00190235
Message ID:
00195180
Views:
25
>>I have done that for previous apps but it requires the machine to have VFP or some DBF editor on their machine. I install most of my apps myself and want a quit way to change the path without having to use anything more than NOTEPAD.
>>
>>I just found a note about using DEFAULT= "your path here" in the CONFIG.FPW and now have that working.
>>
>>
>>I am still stuck on trapping LOCATE DB ERROR. If a DB or table is not in the specified PATH (or more usually, the PATH is bad) VFP must have some way to trap the resulting message before it appears. I checked error codes 1105,1554,1736 but as I mentioned previously, my ERROR HANDLER procedure is not being invoked at all. VFP must consider this more of a notification than an error.
>
>Maybe your form (or form class) has something in its error methods. If it has, it will fire before any general On Error routine. Why don't you put a simple Wait window in form.error, to start with?

I will look into that. Currently I have a form class that has an ON ERROR DO PROG_ERROR_HANDLER... in the INIT. I had not considered the obvious option on the ON ERROR event.

Thanx.
Previous
Reply
Map
View

Click here to load this message in the networking platform