1 Database ( Access ) and 2 Computers running Applications

1 Database ( Access ) and 2 Computers running Applications

Access Database Multiple Connections in a Shared Computer

Multiple connections to a Microsoft Database Access is permitted with the use of ADODB connection. Microsoft Access will create a “.ldb” which is used in a shared environment. Multiple instances of opening Microsoft Access Database are a sample of multiple connections to a single database. Multiple connections to a single database will not permit you to modify tables but you are permitted to add and edit records.

Running applications in separate computers with a single database is impossible when you are not connected to a network. Of course, you can run your application on both of the computers but not using a single database, it will need to use two separate databases just the same file name but not the same database.

If you are eager to pursue this kind sharing back ends, you need to connect your computers into a network. Connecting computers to a network requires you the following hardware:

1. LAN Card

2. UTP Cable

3. RJ45

4. Switch/Hub

You may connect your two computers without using Switch/Hub with the Peer to Peer network topology. Peer to Peer network topology uses the crossover configuration of the cable while the star topology (a network that uses a switch / hub) uses the straight-through cabling. Please refers to the following illustration for the network cable configuration.

Figure 1. Network Cabling Pin Assignment/Configurations.

After you have connected your computers into a network and configured everything including the LAN configurations, create a folder with your Access database on it and share it to your network. For your program or the front-end codes, set your database path at the same folder. That is the shared folder where your database was placed. Use the network name or the shared name of the shared folder of your database instead of the local address used before.

If you can’t afford to purchase network equipment or don’t know how to configure a network or can’t afford to hire a network technician, you will not be able to share your database running in different application run on different computers. Otherwise, we have one option to consolidate your database. First you must identify where you want to put the consolidated database. You can consolidate your database on computer1 and computer2 will be the auxiliary input computer or application.

Here’s how to do it. You need to plan how your application works. How the data were encoded into your database.

Let’s go through an example. Let’s say that you are operating a Retail Store. You need the data of your products. Set A of products will be encoded on Computer A while Set B of products will be encoded on Computer B. Now, you have the data encoded on both computers but different database. Both databases are now in different contents.

Here’s your job. Create a module that will be able to export your database into a CSV (comma separated values) file. Also create a module to import values from a CSV file, where these files can be saved to a USB Flash Drive for easy moving files. Here’s a sample snippet for the project:

Open “exported.csv” for output as #1
      With Products.Recordset
           Do While not .EOF
                 Print #1, !ProductID, !ProductDescription, !ProductCost, !ProductPrice
                 .MoveNext
            Loop
      End with
Close #1

You may also set conditions on the module based on how you implement the module and the structure of the database. You may add an Encoder ID on the table and the Date Encoded field so that the exporting is made easy. It’s up to you how you will implement it.

On the Import side, read all the data into a Comma Separated format from the Exported File and then Save it into your database. This can be done on both sides of your application depending on how you plan the import/export module.

Please find help on how to handle text files using your front end application.