Applicationm with 3 backend-databases

[reidarT]

I have an application with 3 backend databases.
The 3. one is used for history and statistics.
The 1. one is the main database, the 2. is for customers (customerinfo)
I have done this to make the size of the database as small as possible.
Is there any disadvantges with the use of several backend-databases.
The problem is that in a network the saving process takes a lot of time.
(Saving a record)

reidarT

 

[Albert D.Kallal]

There is nothing wrong with your approach.

However, you can't enforce any kind of relational integrity between
different back end files.

Is there any disadvantges with the use of several backend-databases.
The problem is that in a network the saving process takes a lot of time.
(Saving a record)

I would try placing a mde on each workstation, and see if that helps.

In additon, you want to try the persistent connction trick....(this simply
meas that in your startup code, open up a table in the back end file..any
table..and KEEP it open). With 3 mdb files...then you would need to open all
three. Once you do this, then the delay(s) you are talking about should go
away...

I talk about the persistent connection trick here:
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm