Visual FoxPro 6.0 crashes with APPEND BLANK together with Fox 2.6

[filibuster]

Hi,

we are runnung a colorful mixture of Fox 2.6 and Visual FoxPro 6.0. The problem with this cross plattform occurs when Visual FoxPro appends a record to a (shared) table.

APPEND BLANK

creates an "Internal inconsistency error", Visual FoxPro shuts down instantly, and damages the index files - Only a reorganization will help.

Note:
After crashing, VFP still has the table header locked, so that the table will only be accessible (write) after rebooting the workstation.

Any ideas ?

Thanks
Holger

 

[rgbean]

Holger,
There must be more to this than what you are suggesting. We have a major app that is running FPW 2.6a and VFP 6.0 code against the same free tables on both Novell and NT/2000 networks. The APPEND BLANK code is frequently used, and we aren't running into this problem.

What else can you tell us about the VFP code - SP #, buffer mode, private datasessions, table details (# fields, record size)? Does this always happen? Only to certain users? Have you checked the runtime versions (including SP) on each of the workstations? (Don't forget to check the pathing, sometimes there can be multiple version available and they aren't using the one you "think" they are.)

Rick

 

[filibuster]

Hi,

the Fox versions we're using are as follows:
FoxPro 2.6x (DOS)
FoxPro Windows 2.6
Visual FoxPro 6.0 (various SP).

Data Sessions: Not used

Tables: ca. 60 tables open at run-time

One table which is crashing has the following features:
- ca. 250.000 records
- 14 indexes
- 233 fields (7 Memo fields)
- record size: 1765

Total size of all tables: 12 GB.

Number of concurrent users:
- 50 Fox 2.6 Users
- 30 Visual FoxPro Users

The problem only happens under VFP

 

[rgbean]

The only thing that jumps out, is the "VFP 6.0 (various SP)". While normally there aren't many differences in the runtimes under a given version, there were major changes in SP 4. If you are creating the code for the VFP version under SP 4 or 5 and are still using pre-SP 4 runtimes on one or more of those 30 workstations, this may be your problem. Note: Just copying the two runtime .DLL's may not be sufficient to fix the problem - both SP 4 and 5 updated a number of system DLLs (and the MDAC files if any of these components are used). Consider creating a new dummy install set to just upgrade all these files - both the files for the Setup Wizard and Visual Installer have been updated.

Rick