![]() BUT, the one difference I've noticed is that on my machine, on which I've developed the application, it actually does use the NetFileDir created at run time - although the other machines use the entry that was set using BDEAdmin. ![]() (well so I thought)Īt first I thought it may be a peer-to-peer network on 95 problem - but I've tested it here at work on two NT workstations on the network and the same occurs.īoth machines can edit the same record in a table being edited. The Session's Active property is set to true at run-time and the value of the NetFileDir property is changed at run-time. Just to let you know - all the Table components have their Session property set to the value of the Session's SessionName property. Any value assigned to NetFileDir at design time or runtime overrides the BDE configuration setting."Īlthough this is not true - because I write the value of the NetFileDir property to a text file during run-time and it is the value of that the BDE has been set to - not what my application set it to!Īnd according to an article in the developer supportįorum and techincal information database they state that the drive letters need not be the same on all the machines as long as they all inevitably point to the same directory containing the PDOXURS.NET file. "Delphi derives an initial value for NetFileDir from the BDE configuration file for the Paradox driver. ![]() I found this in the Delphi help file regarding the TSession component and the NetFileDir property: I've tried changing the BDE on both machines and it seems thatīoth can still edit the same record at the same time - IE not locking the table when one user puts it into edit mode. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |