Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Forgot to handle 1705
Message
 
 
To
28/10/1998 20:06:12
Man Wai Chang
Hang Hing Metal Manufacturer
Hung Hom, Hong Kong
General information
Forum:
Visual FoxPro
Category:
FoxPro 2.x
Miscellaneous
Thread ID:
00152055
Message ID:
00152057
Views:
27
>I have an application that's not coded correctly
>to handle error 1705, which happened when you try
>to open a DBF that has been exclusively opened by
>another application.
>
>use dbfname shared
>* the codes assumed 100% successful open
>replace field1 with value1
>
>They should have trapped the error and then check
>USED("dbfname") before doing anything (like the
>followings).
>
>on error do errhand with errproc()
>use dbfname shared
>if !used('dbfname')
> return .f.
>endif
>replace field1 with value1
>
>procedure errproc
>parameter m.error
> if m.error=1705
> return
>
>Is there a simple way to work round this problem without
>the need to insert extra codes after _every_ USE sections
>in the system? There could be a hundred of this sections
>littering everywhere in the system.
PROCEDURE mainprogram
ON ERROR DO errhandler WITH ERROR()
USE dbfname IN 0 shared


PROCEDURE errhandler (nerror)
DO CASE
CASE nerror = 1705
    WAIT WINDOW 'File is being in used by another user.  Retrying access...'         NOWAIT
    RETRY
CASE nerror = etc.


ENDCASE
JESS S. BANAGA
Project Leader - SDD division
...shifting from VFP to C#.Net

CHARISMA simply means: "Be more concerned about making others feel good about themselves than you are in making them feel good about you."
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform