Modifying Linked Tables properties

[Guest]

Hi,

I have split my application into FE and BE. When I select a table and then
"Design", a prompt warning me that "...some properties can't be modified" is
displayed...

It asks if I want to continue. If I select "yes", I can go into the table
but it seems to imply that I cannot "change" anything..

Regards
Greg

 

[Allen Browne]

When you split, you have 2 mdb files.

You need to open the back end mdb to make design changes.
The linked tables in the FE will then get the changes automatically.

 

[Smartin]

Hi,

I have split my application into FE and BE. When I select a table and then
"Design", a prompt warning me that "...some properties can't be modified" is
displayed...

It asks if I want to continue. If I select "yes", I can go into the table
but it seems to imply that I cannot "change" anything..

Regards
Greg

I believe you need to open the BE directly.

 

[Guest]

I luv these forums!

Thanks guys.

Regards
Greg

I believe you need to open the BE directly.

 

[david epsom dot com dot au]

The properties that you CAN change are some of the
things like the column order and sort order when you
view the table in datasheet view, which only apply
to your local copy.

But you loose everything anyway if you re-create the link.

(david)

 

[Guest]

Hi Lateral,

Just one more piece of advice on this issue, if I may. Whenever you make a
design change to the BE database, I recommend deleting the linked table from
the FE database, compacting the database, and then re-establishing the link
from scratch (File > Get External Data > Link Tables...). Access caches a
lot of information about the linked table, and this information can easily
become out-of-date if you make design changes to the BE database. I have seen
databases at work that give incorrect query results (and thus incorrect
results on printed reports) when the linked table information was out of
date. The affected queries returned the correct recordset as soon as the
links were deleted and re-created from scratch.

(ACC2000 Optimizing for Client/Server Performance
http://support.microsoft.com/?id=208858

includes the following quote:
"NOTE: If you make changes to fields or indexes on the server, you must
relink the remote tables in Access." I added the parenthesis around the
"ACC2000:" part because this KB article applies equally well to Access 97,
2002, 2003 and the new 2007 (currently in beta).


http://www.granite.ab.ca/access/splitapp/details.htm
includes the following quote:

"Michael Kaplan has posted the following:
One thing you can look at is the deletion/recreation of links. I have been
amazed at how much stuff gets cached in the links for tables, and also how
much of what is cached is based on usage patterns (so that if the two users
make use of a link two different ways, the info might be different). Deleting
and recreating the link can often resolve these weird cases."


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

Thanks Tom,

Regards
Greg

Hi Lateral,

Just one more piece of advice on this issue, if I may. Whenever you make a
design change to the BE database, I recommend deleting the linked table from
the FE database, compacting the database, and then re-establishing the link
from scratch (File > Get External Data > Link Tables...). Access caches a
lot of information about the linked table, and this information can easily
become out-of-date if you make design changes to the BE database. I have seen
databases at work that give incorrect query results (and thus incorrect
results on printed reports) when the linked table information was out of
date. The affected queries returned the correct recordset as soon as the
links were deleted and re-created from scratch.

(ACC2000 Optimizing for Client/Server Performance
http://support.microsoft.com/?id=208858

includes the following quote:
"NOTE: If you make changes to fields or indexes on the server, you must
relink the remote tables in Access." I added the parenthesis around the
"ACC2000:" part because this KB article applies equally well to Access 97,
2002, 2003 and the new 2007 (currently in beta).


http://www.granite.ab.ca/access/splitapp/details.htm
includes the following quote:

"Michael Kaplan has posted the following:
One thing you can look at is the deletion/recreation of links. I have been
amazed at how much stuff gets cached in the links for tables, and also how
much of what is cached is based on usage patterns (so that if the two users
make use of a link two different ways, the info might be different). Deleting
and recreating the link can often resolve these weird cases."


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________