The error message you're getting appears that you stored your database .ind file locally on your stations and is updating only the station's copy but not the .ind file on the server. This will result in a conflict.
When running DP on a network, you can store and run the DP app program from the station but your database's .str, .ind, .txx and data files must all be on the server if you want common access to them. Only the server should have the database files and not the stations. Very important is to make sure all your pointers (DP paths) are mapped to the dp database server including the index. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marcos Favero Florence de Barros Sent: Thursday, July 24, 2008 7:39 AM To: DataPerfect Users Discussion Group Subject: [Dataperf] Networking DP Some help is needed with networking DP. As part of my voluntary work at health centers, I have been trying to set up a network -- something I have never done before. So far I have been able to connect 2 computers with Ethernet cards and MS-Client in a client-server scheme. The network seems to be ok. Then I tested the network with several of my own DP databases, and they all worked perfectly. But when I tried to run the health center database, the following happened: As long as both computers are on the same panel, everything seems to work perfectly. However, if computers are on different panels, then sometimes DP gets stuck with the following error message: DOS error no. 1 Warning The index shows that records are present in the data file, but the file is not found. Do you want to: 1 - Change the Filename (for example, CLASS.DAT to B:CLASS.DAT) 2 - Delete the Index(es) if you have deleted the file. 3 - Exit to DOS and Move or Rename files. Trying to go ahead from here produces messages in unexpected places on the screen. Choosing 1, 2 or 3 has no effect. The only two ways I could find to escape from this are: - Pressing Ctrl-Pause, which sends us directly to the DOS prompt (rather than exiting step by step as with F7). - Going to the other computer and exiting the panel with F7. Once we are back to the panel list, the first computer works normally again. Whether the problem occurs or not depends on which two panels are on the screen. This is consistent, i.e., some pairs of panels always produce the problem, and some pairs never do. I have no idea what is special about the pairs of panels that cause the problem. There are 14 panels altogether. The biggest has 15,000 records, a file of 2 MB, and 6 links, including one recursive data link. The second biggest has 3,000 records in 1 MB and 3 links. These are the most prone to problems. The problem is symmetrical between server and client. As long as the database ran on standalone computers, it behaved perfectly. It has been in full use for over a year now, and I do not recall a single problem related to DP. (By the way, our users -- doctors and nurses -- are really happy about the system.) I replicated the tests at home with exactly the same results, so hardware faults are pretty much ruled out. And, as already mentioned, every other DP database I tested on the same network worked fine, even when placed in the very same folder where the health center database was. Additional information Operating system FreeDOS Memory manager (XMS+EMS) Jemmex.exe (FreeDOS) Shell 4dos.com Hard disk cache Smartdrv.exe (Microsoft) Share Share.com (FreeDOS) Network MS-Client (Microsoft) Protocol NetBEUI DP version 26x Any help will be greatly appreciated! Regards, Marcos Florence Sao Paulo, Brazil _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
