Writing Data to Access Database on Network

[Barry]

Hi

Is the any difference in coding when it comes to standalone database and the
kept on a network?

TIA
Barry

 

[schmrz]

There is no difference in coding the whole application but there is in
connecting. Host is not going to be localhost or 127.0.0.1 anymore, it will
be the ip address of the database host.

 

[Alex Clark]

If you're using the ODBC connector there won't be any difference code-wise,
you'll just change the path in the ODBC connection properties to point to
the .mdb file on the network share instead of on a local drive.

I would be wary of reading/writing to an MS Access database via a network
though. I've seen problems occur, particularly when concurrent writing has
taken place, which required the database to be repaired every other day.

 

[Barry]

I have tested on a network and it works fine, but here is the actual
problem.

I have a Shopping Cart application which uses a Access database.

If i run the app on a standalone system (eg Windows XP) and using another
app developed in C# insert some data into the Access database, i have to
select from a combobox "All Products" int the shopping Cart app, to refresh
the new added data, it shows up, without shutting down the Shopping Cart
app.

However if i use the Shopping Cart App on a network (keep it running) and
insert some data in the Access database using the C# app, the data gets
inserted without any problem into the Access database, but if i select "All
Products" the data is not refreshed, i have to shut down the Shopping cart
app on the network and restart it for the data to appear in the shopping
cart app on the network.

Is there any way i can refresh the data on a network app without shutting it
down. This is my clients requirement not mine, he does not want to shutdown
the shopping cart(s) on the the network.

TIA
Barry