Manually splitting the database

I followed the instructions he
http://support.microsoft.com/?kbid=304932....almost. Instead of linking the
tables first, I imported the queries, forms, etc first.

Would this cause all my queries to break? Because that's what has happened.

It's a simple matter to just do it over in the correct sequence, which I
will try tonight. But in the meantime, I'm just wondering if the sequence of
link tables/import queries makes a difference.

Yes. There are cases where importing queries to non-existent tables yields
unusable results.

Delete the queries, make sure Name AutoCorrect is off, compact, import the
tables, and then import the queries again.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Gitche Gumee" wrote in message
...
I followed the instructions he
http://support.microsoft.com/?kbid=304932....almost. Instead of linking
the
tables first, I imported the queries, forms, etc first.

Would this cause all my queries to break? Because that's what has
happened.

It's a simple matter to just do it over in the correct sequence, which I
will try tonight. But in the meantime, I'm just wondering if the sequence
of
link tables/import queries makes a difference.

=?Utf-8?B?R2l0Y2hlIEd1bWVl?=
wrote in :

I followed the instructions he
http://support.microsoft.com/?kbid=304932....almost. Instead of
linking the tables first, I imported the queries, forms, etc first.

Would this cause all my queries to break? Because that's what has
happened.

What you need to end up with is one file with a bunch of tables in it; and
another file with a load of reports and forms etc, and linked tabledefs
pointing at the bunch of tables in the other file. It doesn't matter what
order you go about it: you can rip the UI features out of the tables mdb,
or you can rip the tables out of the UI.

Have you forgotten to Get External Data Link Tables in your new UI file?
As long as the links have the same name as the original tables did, then
the queries and forms etc will just use those links without noticing any
difference.

Hope that helps


Tim F

I linked the tables. The queries seem to be oblivious to that. In query
design view there are no relationships between the tables and all of the
field names in the query have been converted to expressions.

"Tim Ferguson" wrote:

=?Utf-8?B?R2l0Y2hlIEd1bWVl?=
wrote in :

I followed the instructions he
http://support.microsoft.com/?kbid=304932....almost. Instead of
linking the tables first, I imported the queries, forms, etc first.

Would this cause all my queries to break? Because that's what has
happened.

What you need to end up with is one file with a bunch of tables in it; and
another file with a load of reports and forms etc, and linked tabledefs
pointing at the bunch of tables in the other file. It doesn't matter what
order you go about it: you can rip the UI features out of the tables mdb,
or you can rip the tables out of the UI.

Have you forgotten to Get External Data Link Tables in your new UI file?
As long as the links have the same name as the original tables did, then
the queries and forms etc will just use those links without noticing any
difference.

Hope that helps


Tim F

Thanks. I'll try that before running the whole process again and will report
back.



"Allen Browne" wrote:

Yes. There are cases where importing queries to non-existent tables yields
unusable results.

Delete the queries, make sure Name AutoCorrect is off, compact, import the
tables, and then import the queries again.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Gitche Gumee" wrote in message
...
I followed the instructions he
http://support.microsoft.com/?kbid=304932....almost. Instead of linking
the
tables first, I imported the queries, forms, etc first.

Would this cause all my queries to break? Because that's what has
happened.

It's a simple matter to just do it over in the correct sequence, which I
will try tonight. But in the meantime, I'm just wondering if the sequence
of
link tables/import queries makes a difference.

Deleting the queries and then re-importing them did the trick.

Thanks.

"Allen Browne" wrote:

Yes. There are cases where importing queries to non-existent tables yields
unusable results.

Delete the queries, make sure Name AutoCorrect is off, compact, import the
tables, and then import the queries again.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Gitche Gumee" wrote in message
...
I followed the instructions he
http://support.microsoft.com/?kbid=304932....almost. Instead of linking
the
tables first, I imported the queries, forms, etc first.

Would this cause all my queries to break? Because that's what has
happened.

It's a simple matter to just do it over in the correct sequence, which I
will try tonight. But in the meantime, I'm just wondering if the sequence
of
link tables/import queries makes a difference.

=?Utf-8?B?R2l0Y2hlIEd1bWVl?= wrote
in :

I linked the tables. The queries seem to be oblivious to that. In query
design view there are no relationships between the tables and all of the
field names in the query have been converted to expressions.


Can you post the "before" and "after" SQL of the queries? It sounds very
strange to me.

What happens when you open the back end database (the one with the actual
tables still in it)? Are the relationships still visible there in the
Relationships window? As long as they are there, then it doesn't matter
whether the front end sees them or not: the engine will still refuse to
make any updates that break the RI constraints.

Best wishes


Tim F