About using Access database as a server

Some time ago, I used Delphi as a standalone version of the software. The database was accessed, and the development process was quite smooth. How can we know what is unpredictable? One day the customer proposed to run the software in the network environment! I believe many of my friends have encountered such problems. Now there are three ways to go, one is to upgrade the Access database to the SQL Server database, and the other is still using

Some time ago, I used Delphi as a standalone version of the software. The database was accessed, and the development process was quite smooth. How can we know what is unpredictable? One day the customer proposed to run the software in the network environment! I believe many of my friends have encountered such problems. Now there are three ways to go, one is to upgrade the Access database to the SQL Server database, and the other is still using

Some time ago, I used Delphi as a standalone version of the software. The database was accessed, and the development process was quite smooth. How can we know what is unpredictable? One day the customer proposed to run the software in the network environment!

I believe many of my friends have encountered such problems. There are three ways to go, one is to upgrade the Access database to the SQL Server database, and the other is to still use Access, but so that it can share data on the network, the third article is what we will discuss today, transforming Access into a database server!

I used the simplest method at the time. We suggest you put the software in a fully shared folder and create a shortcut for the machine to use. Hey, the biggest benefit of this method is that I don't have to worry about it any more.

Later I thought, could I convert the Access database into a server-like version?

This method has the following advantages: 1. You do not need to install Windows Server or SQL Server. These software is difficult to install, expensive, and requires high machine configuration; 2. Ease of Client installation and configuration.

I immediately thought of the MIDAS technology (now renamed DataSnap ). Can I create an application server to convert the Access database to a server version?

I will test transformation right away. Select a machine as the server (preferably WIN98 or later operating system), use Socket connection mode, put the Access database on it, and run the application server software transformed by DataSnap technology once, then copy the client software to another machine for running.

There are two points to note: first, scktsrvr must be run on the server. This program has its own Delphi, and second, it must copy the file ". net. dll" to the system folder of the client.

The results are confusing. The client can read the data on the server, but cannot submit the changes!

The original data connection uses Jet. OLEDB.4.0. Remember that when I used BDE for testing, even common DBF Files can be used as servers. Will the problem be solved here?

So I configured a connection to the Access Database in ODBC, and then used the Database component of BDE to select the Database alias and re-test it. This time, everything is normal and successful!

The next problem is the packaging of BDE and ODBC. These two configurations are troublesome and can be implemented by modifying the registry using a program, but there are simpler methods. Many Installation Tools now have the ability to automatically configure BDE and ODBC. You may wish to use these tools for packaging. In addition, because multi-layer database development is used, you only need to configure it on the server once, and the client only needs an additional file named ". DLL.

This is the result of my own experiment. I don't know who else has a better method.