On 2013-08-13 09:31, Bruce wrote: > a) MSAccess did/does not run as a server process, especially to remote > machines. In order to get it to that we had to use ODBC and establish > a connection process on the "server" and similarly an ODBC client on > the remote "client" machine. In the case of a single connection to the > "server" this was reasonably trivial, but if multiple "clients" were > involved this bordered on a nightmare.
This can't be stressed enough. Furthermore, if Access is actually running on the remote machine as Ivan said, that counts as a client. If you access the database via ODBC at the same time as through Access itself, whether your ODBC client is VB, Gambas or anything else, you risk corruption. Like sqlite, Access is designed for single-user data storage, even if Microsoft has added features over the years to make it seem otherwise. I did a project exactly like this about 8 years ago, and we ended up moving the data into a MySQL server, converting the tables to ODBC links using some Access macro we found in a MySQL forum, and accessing the MySQL data natively from Gambas and a web inquiry system. Even so, Access misbehaved constantly and made it a nightmare. Multi-user networked database applications need a multi-user networked database server. Period. Rob ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
