I have developed an application in VB.NET that works with MS Access database. I installed this software on one PC (Windows 7), which is considered as the server, since it is hosting the database sharing it on the local network. The empty database file is installed together with the other files of my deployment project package, which is a part of my VB.NET solution. The software works fine on this machine.
Then, I installed the software on a different workstation (Windows XP). The connection to the db is established without troubles, except for the unpleasant detail that no records created by the server's application are visible.
Besides, when I open the database file and check any table, no entry appear either (neither openning the file on the workstation, nor on the server itself). The structure of the tables is OK, though.
In other words, the data registered by the server's software can only be viewed through the server's software. And the data inserted by the other workstation or openning the db file directly can be viewed anywhere, except through the server's software.
I have revised the Windows 7 permissions for the db folder and file to accept remote connections. So did I for the db MS Access properties. The ConnectionString I use for the software to work with the db had always worked fine in other client-server applications with MS Access.
I suspect there's a sort of a data protection mechanism that comes either with Windows 7 or with MS Access 2007. Or I should definitely deploy the db file separately from the other software dependecy files (thing I have not tried yet).
Any advices on this case will be appreciated a lot, because my patience is beginning to run out.
0 · ·