Create Index in Different MDB

[PurpleUnicorn]

I need to merge a couple of large mdbs. I was hoping to create one mdb to coordinate it all.

I will need to create indexes, create new mdbs, and summarize data and build new tables.

Is it possible to create indexes on tables that reside in a different mdb? Once this is resolved, I think I can figure out how to do the rest.

Thanks

 

[BNPMike]

What are you doing? Are you merging mdbs into one or not?

It is not possible to create an index which covers more than one table under any scenario. When you say 'index' do you mean a thing which enhances access efficiency or do you mean something that enforces uniqueness? I suspect it's the latter you're worried about.

 

[PurpleUnicorn]

I receive "raw" data that needs to be manipulated.

I want to create a database that can connect to each of my "raw" data mdbs and create the appropriate indexes on each of the tables.

I can already automate this from within each of the "raw" data mdbs. I have a form that cycles through all of the tables in the mdb and creates an index on each table.

However, I don't want the user to have to open 4 or 5 different mdbs to create indexes. I would like to do it all from one "master" mdb.

Once all of the indexes are created, I want to link to all of the tables and manipulate the data.

 

[BNPMike]

If you create an index on a table (which presumably is the format in which you are storing your 'raw' data) it will persist without any further action on your part. I suspect you are importing into fresh tables every time. If so, there is no point in doing that. You can automate emptying the tables from your front-end database and reloading them from perhaps staging tables used to import the raw data. The downside is you may have wasted tablespace and index space depending on when you can compact the database after emptying the tables.

It is still not clear whether you are building one physical master database or a virtual one. If physical is OK then just link to the others and load in the data.

Why are the databases separate anyway? Is it a question of size limits? If so maybe you should be using MSDE, Oracle MySQL etc. Jet is not intended for very large databases.