Fox 2.6 on Unix server

[wawalter]

Hello,

My company recently moved our production server from a Windows server to a Unix server, a EMC Celerra NAS. I am now frequently getting corrupted indexes on a legacy program that had previously rarely had any problems. I have to erase the cdx file and recreate all the indexes. The executable code and dbfs all reside on the new server.

Has anyone else had this problem or have any ideas? I'm not sure the server move is the problem, but nothing else has recently changed so I'm guessing it may be.

Thanks,
Bill

 

[DSummZZZ]

Does this server have a Windows compatible file system?


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[wawalter]

It uses CIFS via Samba according to our network admin. Thanks

 

[DSummZZZ]

So does that mean it's a Windows compatible file system?
More specifically, a DOS 8.3 compatible file system?
Even a FAT32 or NTFS compatible file system should work.
I don't know anything about Samba, CIFS, EMC Celerra NAS, or Unix servers.

The reason I ask, is if it isn't, files locks, record locks, block lengths and so on are just not going to be recognized or interpreted the same by Foxpro, unless you are now using Foxpro for Unix.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[wawalter]

It is supposed to be fully windows compatible. I just find it strange that it is still mostly working, just an occassional problem.

I think for the time being I will just rewrite the two main order screens so not as many people will be hitting the tables, then come back when resources allow and move the rest of it to our current production platform.

Thanks for you help.

Bill

 

[jacinc2]

If it is Foxpro for Windows/DOS
-----Move to Foxpro for Unix.
If it is Foxpro for Unix and you are still getting this, then you need to secure your LOCKING ROUTINES.

Find the API that controls TTS Mechanism for Unix.
TTS stands for Transaction Tracking System.
After you get the API use its routines to LOCK, COMMIT, ROLLBACK AND UNLOCK records and files in Unix.

This should fix your problems 100%.

By using these lock routines, you eliminate the problem with FoxPro's physical locking of the CDX/IDX Tags, which is why your index files are going wacky.

I just fixed this problem with a Novell Server which has a good TTS routine, but Foxpro 2.x or less need exteranl API to opperate the OSs TTS System, same as Unix does.


Good luck.

Johnny