Question regarding linked tables in Access 2003

[Tony]

Hi All,

I have an Access 2003 database that pulls data from a Progress database
every night for the purpose of populating tables in Access that can be used
to populate combo boxes in another application. One of the Progress tables
from which we pull data has in excess of 500,000 records, about 200,000 of
which we pull over. I've noticed that when this process runs (via a script
invoked by a Windows scheduled task), that an additional linked table is
created in Access for the Progress table that has the 500,000 + records.
For example, if the linked table in Access is named 'PUB_progressTableName',
another linked table named 'PUB_progressTableName1' is created.

Does this sound normal based on the size of the Progress table and the
number of records we pull from it? I'd rather not have to open the Access
database every morning simply to purge this table. I suppose I could add
code to the script that runs this process that will check for the additional
linked table and delete it if it finds it, but that doesn't seem like a very
elegant solution.

Any feedback that can be offered is appreciated.

Thanks & Ciao

 

[John W. Vinson]

Hi All,

I have an Access 2003 database that pulls data from a Progress database
every night for the purpose of populating tables in Access that can be used
to populate combo boxes in another application. One of the Progress tables
from which we pull data has in excess of 500,000 records, about 200,000 of
which we pull over. I've noticed that when this process runs (via a script
invoked by a Windows scheduled task), that an additional linked table is
created in Access for the Progress table that has the 500,000 + records.
For example, if the linked table in Access is named 'PUB_progressTableName',
another linked table named 'PUB_progressTableName1' is created.

Does this sound normal based on the size of the Progress table and the
number of records we pull from it? I'd rather not have to open the Access
database every morning simply to purge this table. I suppose I could add
code to the script that runs this process that will check for the additional
linked table and delete it if it finds it, but that doesn't seem like a very
elegant solution.

Any feedback that can be offered is appreciated.

Thanks & Ciao

If it's a linked table, there's nothing to "purge". Your database only
contains a pointer to the Progress table, not the data itself.

It's not clear how your script is working, but your suggestion of deleting the
link if it's found is a sound one. You may also want to simply drop the link
after the import is completed.

John W. Vinson [MVP]

 

[Tony]

John,

Thanks for the reply. I'm going to have to keep an eye on this to see if I
can find what's triggering the behavior, but it sounds like it's not that
big of a deal. I know that its just a pointer, but I'd prefer to have as
few objects in the dB to keep things as tidy as possible.

I appreciate the feedback.

Tony

 

[John W. Vinson]

John,

Thanks for the reply. I'm going to have to keep an eye on this to see if I
can find what's triggering the behavior, but it sounds like it's not that
big of a deal. I know that its just a pointer, but I'd prefer to have as
few objects in the dB to keep things as tidy as possible.

Feel free to post the script that you're running; maybe there's something that
will explain this effect.

John W. Vinson [MVP]