By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,495 Members | 1,208 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,495 IT Pros & Developers. It's quick & easy.

Struggling with linked database problem

P: n/a
Hi all,

I've got a Front End / Back End database that was working just fine.
One day i opened the FE to find that if I tried to open one of the
linked tables from the database window, nothing happened (hourglass
for about 2 seconds then nothing).

I tried relinking the tables and got the same response. (Access even
completely bombed out once with a Dr Watson failure).

So I created a new, blank database and just linked to the BE again, no
other queries, code or anything, just linked tables. The same problem
occurred. This led me to think that the problem must lie with the BE
database.

So i exported, in csv format, all the tables from the database. Then
recreated the BE database with just the data tables imported from the
text files.

Then created a brand new database and only linked to the new BE
database.

....

SAME PROBLEM

....

I'm at my wits end as i have gone back to the most basic level and
still have the problem of the linked FE not allowing an open of the
tables. I have also discovered that i cannot delete the link from the
new FE table either.

I do have a separete FE/BE database and that continues to work fine.
Both of the database BEs exist on the same network server and the FEs
exist on peoples desktops.

Everyone else now has the same problem with the linked tables...

Any ideas? I noticed a thread on this from Jan but it didn't get many
responses...

P.S. using Access 2000 on NT4.
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Firstly, make sure you have the latest service pack for your version of
Access by visiting:
http://support.microsoft.com/default...VER&style=home
You should also have the latest Jet service pack (SP8).

After that, follow these steps to re-create the back end and front end:

1. Create a new (blank) database.

2. Uncheck the boxes for Name AutoCorrect under Tools | Options | General.

3. Import all the tables from the back end.

4. Open each table in design view. Open the Properties box (View menu), and
set Subdatasheet Name to:
[None]

5. Make sure that the path, file, and table names are not too long. For
example, shorten the fully qualified path/file name if it is greate than 128
characters.

6. Create another new database.

7. Uncheck the boxes for Name AutoCorrect under Tools | Options | General.

8. Import all objects from the front end *except* the linked tables.

9. Link the tables from the newly created back end file, using File | Get
External | Link (rather than the linked table manager). If the back end is
on a server, you can get to the network through the File Open dialog.

10. Open a code window, and set the right references (Tools | References).
Compile (Debug menu in a code window).

If you still have the same problem with these new databases created without
the problem issues and on the latest service packs, it must be a networking
problem. You could test that theory by deleting the linked tables, moving
the data file onto the local hard disk, and relinking.

--
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.
"Robert McGregor" <rm*******@firenet.uk.com> wrote in message
news:8d************************@posting.google.com ...
Hi all,

I've got a Front End / Back End database that was working just fine.
One day i opened the FE to find that if I tried to open one of the
linked tables from the database window, nothing happened (hourglass
for about 2 seconds then nothing).

I tried relinking the tables and got the same response. (Access even
completely bombed out once with a Dr Watson failure).

So I created a new, blank database and just linked to the BE again, no
other queries, code or anything, just linked tables. The same problem
occurred. This led me to think that the problem must lie with the BE
database.

So i exported, in csv format, all the tables from the database. Then
recreated the BE database with just the data tables imported from the
text files.

Then created a brand new database and only linked to the new BE
database.

...

SAME PROBLEM

...

I'm at my wits end as i have gone back to the most basic level and
still have the problem of the linked FE not allowing an open of the
tables. I have also discovered that i cannot delete the link from the
new FE table either.

I do have a separete FE/BE database and that continues to work fine.
Both of the database BEs exist on the same network server and the FEs
exist on peoples desktops.

Everyone else now has the same problem with the linked tables...

Any ideas? I noticed a thread on this from Jan but it didn't get many
responses...

P.S. using Access 2000 on NT4.

Nov 12 '05 #2

P: n/a
Thanks for the respone...

It was in fact the filename length that was causing this... never come
across this before. The full path and filename came to 138 characters.

I reduced the name of the file and the name of the last two
directories in the tree and it all worked perfectly straight away.

Genius all round!

Tahnks again,

Rob.

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message news:<3f**********************@freenews.iinet.net. au>...
Firstly, make sure you have the latest service pack for your version of
Access by visiting:
http://support.microsoft.com/default...VER&style=home
You should also have the latest Jet service pack (SP8).

After that, follow these steps to re-create the back end and front end:

1. Create a new (blank) database.

2. Uncheck the boxes for Name AutoCorrect under Tools | Options | General.

3. Import all the tables from the back end.

4. Open each table in design view. Open the Properties box (View menu), and
set Subdatasheet Name to:
[None]

5. Make sure that the path, file, and table names are not too long. For
example, shorten the fully qualified path/file name if it is greate than 128
characters.

6. Create another new database.

7. Uncheck the boxes for Name AutoCorrect under Tools | Options | General.

8. Import all objects from the front end *except* the linked tables.

9. Link the tables from the newly created back end file, using File | Get
External | Link (rather than the linked table manager). If the back end is
on a server, you can get to the network through the File Open dialog.

10. Open a code window, and set the right references (Tools | References).
Compile (Debug menu in a code window).

If you still have the same problem with these new databases created without
the problem issues and on the latest service packs, it must be a networking
problem. You could test that theory by deleting the linked tables, moving
the data file onto the local hard disk, and relinking.

--
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.
"Robert McGregor" <rm*******@firenet.uk.com> wrote in message
news:8d************************@posting.google.com ...
Hi all,

I've got a Front End / Back End database that was working just fine.
One day i opened the FE to find that if I tried to open one of the
linked tables from the database window, nothing happened (hourglass
for about 2 seconds then nothing).

I tried relinking the tables and got the same response. (Access even
completely bombed out once with a Dr Watson failure).

So I created a new, blank database and just linked to the BE again, no
other queries, code or anything, just linked tables. The same problem
occurred. This led me to think that the problem must lie with the BE
database.

So i exported, in csv format, all the tables from the database. Then
recreated the BE database with just the data tables imported from the
text files.

Then created a brand new database and only linked to the new BE
database.

...

SAME PROBLEM

...

I'm at my wits end as i have gone back to the most basic level and
still have the problem of the linked FE not allowing an open of the
tables. I have also discovered that i cannot delete the link from the
new FE table either.

I do have a separete FE/BE database and that continues to work fine.
Both of the database BEs exist on the same network server and the FEs
exist on peoples desktops.

Everyone else now has the same problem with the linked tables...

Any ideas? I noticed a thread on this from Jan but it didn't get many
responses...

P.S. using Access 2000 on NT4.

Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.