Under Win 2K/XP dBase 5 apps refuse to create record until quited!

[wisboss]

I've had many years of successes writing dBase V DOS applications running under Win 3.x, 95 and 98 in a Novell LAN environment until now. My problem is: if the application runs under Win 2000, or XP, the record created by the application on a client machine will not be written to the dbf file until you quit dBase. In such cases, on a client machine you can see the record created, you can modify it, browse it, calculate it etc., but other users on the network can't see it or share it because the record is in the memory of the client matchine without being committed to the database. I played with the memory related Novell client settings, Windows settting and nothing seems to work. Anybody have similar experiences or clues of solution?

 

[Guest_imported]

Here are my experiences from previous posts. There doesn't seem to be much mention of the record locking problems on this forum and I can only assume that most of the participants are not working with multi user systems.

David.


DJClarke (Visitor) Aug 10, 2001
My Client is currently introducing New computers (Win 2000 Pro) to their dBase IV Payroll system. The problem occurs when several users try to append records to the same database at the same time. The user with the Win2K pro computer will wipe out all of the updates made by the Win98 user. Two Win2K Pro users will selectively wipe out each others work. The Win 2K Pro computer ignors all record locks and other user updates. It almost appears like WIN 2K Pro makes a copy of the datafile when opened, then writes the file back when it is closed. The Clipper DBCOMMIT() command solves this problem (In Clipper). The AutoSave setting in dBase has no effect. This problem only seems to occur when appending records, editing existing records does not seem to be affected. I have discovered an inelegant solution: Close the datafile before and after appending a record. It seems to me there should be a way to change WIN2KPro so that it handles dBase files like WIN98, otherwise I have a huge coding job ahead.



billfw (Visitor) Jun 3, 2002
I seem to have the same problem did you find a better solution.

Thanks

DJClarke (Visitor) Jun 10, 2002
In the Fall I thought I had the problem solved when I heard about a solution on a different BB. They believed that using two protocols at once, screwed up the record locking of Win2000Pro. In our case we were using IPX (novell) and IP (internet). I was easily able to duplicate the problem in my office when using the two protocols. When I removed IPX, the problem disappeared (In my Office). So we moved several Districts to a WIN 2000 Server (IP only) and let them loose. Although much improved, this spring I have been getting reports of the same old problem happening during times of heavy data entry. (3-4 users appending records to the same data file). It has been very frustrating with the lack of info and interest in this problem. (one response in 10 months). A lot of my reports are already programmed in clipper so I guess that I will have to recode (in Clipper) the problem areas of my dBase program.

My original solution dating back to last summer was to open and close files before and after appending data. (flush buffers). This worked great at first, but after a few months I noticed that the targeted data files were becoming corrupted very frequently (Missing EOF marker). I restored the original code and the ongoing corruption ended.

 

[RHankinsJr]

Win 2000 and XP assume they are the only workstations that are using a file. You may want to check into doing ODBC connection to the file thru your Control Panel Richard L. Hankins Jr.
Senior Programmer
Auction Services, Inc.

 

[my2Cents]

Hi guy

Why not pose this unique problem to the experts at Dbase.com newsgroup. I am sure you will get immediate attention. And a problem that needs to be addressed. After reading your post it scares me. I was planning on codeing for several agencies but I don't need a headache like this.

If you do get some relief please come back and post your soultion.

Thanks

my2Cents

 

[cfneumann]

In the (16-bit) BDE settings, do you have LOCAL SHARE = TRUE on the SYSTEM tab? Christopher F. Neumann
[dBASE Charter Member]
Blue Star Visual dBASE graduate
ICCP certified TCP/IP Network Analyst

http://members.aol.com/noahcneumann