Linked Tables

[JC3]

Hi,

I use a number of tables as data for Combo boxes (i.e. Equipment List, Site Lists etc.).

Using these directly linked to the BE DB was quite slow so therefore I run queries on startip of the DB to copy the data from the BE to the FE and base the queries on the FE. This all works fine and I have no issues with this.

My questions is mainly in regard to the redundant linked tables. Do these have an effect both memory and performance wise after the initial update?

If so, am I better using a recordset update to populate the FE tables on startup and deleting the linked table and append query?

What is the recommended best way to deal with this kind of issue?

Regards

JC

 

[gemma-the-husky]

i don't think they affect performance.

i wouldn't delete them - you only have the bother of recreating them next time you open the dbs. you can set the table attribute as hidden if you don't want to see them in the table list

currentdb.TableDefs("mytable").Attributes =
currentdb.TableDefs("mytable").Attributes + dbhiddenobject

 

[modest]

Hi,

I use a number of tables as data for Combo boxes (i.e. Equipment List, Site Lists etc.).

Using these directly linked to the BE DB was quite slow so therefore I run queries on startip of the DB to copy the data from the BE to the FE and base the queries on the FE. This all works fine and I have no issues with this.

My questions is mainly in regard to the redundant linked tables. Do these have an effect both memory and performance wise after the initial update?

If so, am I better using a recordset update to populate the FE tables on startup and deleting the linked table and append query?

What is the recommended best way to deal with this kind of issue?

Regards

JC

This post was from a while ago, but I just wanted to address the common forum viewer. For any transaction based table or any table that you will being using DML statements on (e.g. updates, deletes, etc), if there are multiple front ends then it is important not to transfer tables from the BE to the FE. This can cause many performance issues, including data redundancy and data integrity problems.