Temporary tables causing bloating

[jedda]

Hi,

I have a design problem.

I have an application that uses VBA and ADO to connect an Excel front end to a JET back end. It's far from ideal, but it's the best solution I can come up with given the circumstances.

The back end consists of a number of permanent tables, but also 3 temporary tables that have all records deleted and repopulated daily.

This is bloating the back end. I'm compacting frequently, but I'd like to work around this issue.

I've thought about splitting the back end, but I need to run queries that involve both the permanent and temporary tables.

Any help would be appreciated.

 

[Joe4]

This is bloating the back end. I'm compacting frequently, but I'd like to work around this issue.

How frequently? I have many databases set to "Compact on Close", so it does it automatically every time the database is closed.

I've thought about splitting the back end, but I need to run queries that involve both the permanent and temporary tables.

Splitting the back-end shouldn't prevent that. You can just link them altogether in whatever database you are performing your queries in.

If the size of your data is really becoming an issue, you may need to investigate using a different back-end to house your data tables, like SQL or Oracle.

 

[jedda]

Joel, thanks for your reply.

I'm compacting the database daily using JRO by manually running a separate macro in the Excel front end.
I've held off on automatically compacting due to the possibility of other front ends competing for use of the database, but it is an option.

So far I have not had any corruption issues, but I still regard my present approach as being poorly designed.

I'm looking into linking tables from different databases using ADO at the moment. (Can anyone link to a good walkthrough of how this is done?)

Unfortunately in this case I am unable to use a client-server DBMS. It would definitely be my preference to get someone to set this up for me if this were possible.

 

[Joe4]

I'm compacting the database daily using JRO by manually running a separate macro in the Excel front end.

You will need to compact the database holding your temporary tables to keep it from bloating (wherever) they reside.

I'm looking into linking tables from different databases using ADO at the moment. (Can anyone link to a good walkthrough of how this is done?)

If all the tables reside on the same network in other Access databases, you should be able to link to them directly through the Access table objects. I don't think you need any special ADO code to do that.

 

[jedda]

Joe4, thanks for your help. I've managed to find a solution here.
http://www.msdn.microsoft.com/en-us/library/aa164914(v=office.10).aspx