Network crash - Paradox 10

[sloinc]

Using Paradox 10 on peer to peer network with 5 work stations, soon expanding to 10. Am having problems with system lockups. All data transaction files are on file server (Windows 2000 Pro) in one directory (":main:tablename.db&quot with all work stations mapped to that alias directory. Each work station (Windows 98)has a directory for data input tables alias(":local:tablename.db&quot and a directory for forms and reports. Needed records are TCursored from (":main to (":local then tc.close() all main and local tables. The process is reversed to store new or modified records at (":main.

I can not determine if this is a record lock problem, operating system, or something else.

I appreciate any help in advance.

 

[footpad]

sloinc,

I'm sorry, but I'm being a little slow this evening. Can you provide a few more details about the actual problem you're facing? You mentioned system lockups, but you didn't provide any details about the lockups or the operations that lead to them.

Thanks in advance...

-- Lance

 

[sloinc]

Lance-

Appreciate you taking the time!
All workstations are running Paradox. Main form, not menu, uses push buttons to call security form to determine if user can access to data input form. With verification, the security form calls data input form. User performs task, either leaving the form active at that work station or closing the form to return to the main form.

All forms and (":local: tables are running independent on each work station or all forms and data input files are resident on each work station and independent of all other work stations. All calls and puts to the file server are for specific records in the tables not whole tables.

Any one of the five (5) work stations could have made a call to a table on the server that locked up Paradox. When this occurs the server locks up. The only known solution is to shut down the system and restart the file server first then the work stations.

 

[footpad]

sloinc,

Hm. The hard part is going to be figuring out why the server is locking up. I've seen environmental things, but nothing that is a known cause of lockups.

You might verify that Optimistic Locks are disabled on the server. You might also check out

http://www.thedbcommunity.com/faq/29.htm

and

http://www.bdesupport.com/stability.htm

for additional server configuration ideas.

Barring any of those, you'll need to nail down the operation that's causing the lockup. Perhaps adding a bit of logging would help. Basically, you maintain a text file on your local machines that write status notes before and after major operations. That way, you can review the logs and see which operations were in process when the server locked up.

Also, have you applied the latest service packs for Paradox 10 (

http://www.corel.com/support/downloads/index.htm)?

Hope this helps...

-- Lance