Tables separate from other objects

[Guest]

Hi,

I am currently building a desktop database application that is LAN based and
will be used by many users at the same time. I started with the assumption
that it is best to separate the data tables in a separate database and build
the queries, forms, reports, and VB code in another database which links to
the tables in the first one.

I have noticed that the main database is slow to access the linked tables,
probably because they link over the LAN. That led me to question this method
and I am wondering if it would be best to keep it all together.

Any of you have advices on this subject?

Thank you.

 

[Pieter Wijnen]

No, But you may want to keep a persistant connection to the BE.
My preferred way to achieve this is to open a hidden form as part of the
startup process & add code similar to this:

Dim GlobalRs AS DAO.Recordset

Private Sub Form_Open(Cancel As Integer)
Set GlobalRs = Db.OpenRecordset("SELECT 'X' From MyTable Where
1=0",DAO.dbOpenSnapshot)
End Sub

Private Sub Form_Close()
GlobalRs.Close : Set GlobalRs = Nothing
End Sub

HTH

Pieter

 

[John W. Vinson]

Hi,

I am currently building a desktop database application that is LAN based and
will be used by many users at the same time. I started with the assumption
that it is best to separate the data tables in a separate database and build
the queries, forms, reports, and VB code in another database which links to
the tables in the first one.

I have noticed that the main database is slow to access the linked tables,
probably because they link over the LAN. That led me to question this method
and I am wondering if it would be best to keep it all together.

Any of you have advices on this subject?

Thank you.

Absolutely, have them split; corruption and database contention will be much
reduced. See http://www.granite.ab.ca/access/splitapp.htm for some pointers on
how best to do this.

John W. Vinson [MVP]