Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Network usage problem when upgrading from VFP 5 to VFP 7
Message
From
12/08/2003 11:46:49
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Network usage problem when upgrading from VFP 5 to VFP 7
Miscellaneous
Thread ID:
00819406
Message ID:
00819406
Views:
59
Hi there,

We are experiencing a problem with our VFP application. There is an intermittent problem happening that kills our application at one plant location only. The users get the following error when doing inserts/updates to the database:

File Access Error - You don't have permission to update this applications data table. Please notify your network Administrator

Here are the facts:

1) We upgraded our shop floor application from VFP 5 to VFP 7
2) Back end database is Fox *.dbc
3) End users are running a mixed environment, data collection being done mostly on Windows 95
4) End users each have a 10 meg shared network connection
5) Other plant locations that have 100 meg network connections don't see this problem at all.
5) Error seems to happen when network usage is at a peak (in the afternoon)

There seem to be a small variety of errors that can happen:

1) When the error gets into our error routine and writes to the error log table, we see the following message:"Error 2028: API caused an exception"
2) Sometimes the operators see the application die doing the same save routine but the errors don't get written to the error log. The Fox app dies before the error routine can write the error to the table.
3) The following error has also been seen: "Program Error 2028 - Program frmdatacol.macheset - code - 1478fmw"
4) There have been other errors, but I can't find the exact verbage at this time.



My older application written in VFP 5 didn't experience this problem at all.
We only see it with the upgraded VFP 7 application. The source code did not change, so I'm wondering if VFP 7 does something different that VFP 5. I'm sure that the "shared 10 meg" connections are contributing to this problem, but there's no way to get around that obstacle at the moment...there's no money available to change the network in any fashion at the moment.

I'm just a programmer, so I'm somewhat out of my element trying to troubleshoot this problem. Any suggestions would be greatly welcomed.

Thanks for reading,

Joe
Next
Reply
Map
View

Click here to load this message in the networking platform