Linked databases

[Glynn]

I have packaged a LINKED database system using the MS 2003 Developer
Extension Packaging Wizard, that works fine but on installing the system on a
client XP I get the following message:
C:\Users\Glynn\Documents\Access Databases\Trust Accounting\Linked
databases\db1.mdb is not a valid path

In explanation - the above is the path in the Front-end database - Glynn
being me, and Trust Accounting being the original DB file.

I'm fairly sure the problem does not lie in the Packaging Wizard - as
nowhere in the that Wizard have I input the above Path.

Packaging an UNLINKED file is no problem.

I have created the LINKAGE by Creating a Back-end blank Dtabase (db1.mdb) -
then importing the Tables from the Front-end DB to the BE, then next,
deleteing all the Tables in the FE, then finally LINKING the FE to the BE.

The purpose is to facilitate distributing system changes/upgrades to Users,
who have installed the Linked system - so that with the Data stored in the
BE, system changes only affect the FE, and the Users data remains unaffected.

Would appreciate help.

 

[Alex Dybenko]

Hi,
you need to implement your own relinking procedure in your application,
something like this:
http://www.mvps.org/access/tables/tbl0009.htm

--
Best regards,
___________
Alex Dybenko (MVP)
http://accessblog.net
http://www.PointLtd.com

 

[Armen Stein]

Hi,
you need to implement your own relinking procedure in your application,
something like this:
http://www.mvps.org/access/tables/tbl0009.htm

Or ours. You're welcome to use our free J Street Access Relinker on
our J Street Downloads page: http://ow.ly/M56Q

It handles multiple Access back-end databases, ignores ODBC linked
tables, and can automatically and silently relink to back-end
databases in the same folder as the application (handy for work
databases or single-user scenarios). There's a ReadMe table with
instructions.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

 

[Glynn]

When I look at your code - it is frightening to realise how little I know -
however 'nil desperantum'.

The question now is - how do I apply your code.

I have loaded the J Street Relinker into my Modules of the Front-end
database - but how do I activate its functionality.

Please be patient, and explain (to a dummy) the steps to activate.

Appreciate your help.

 

[Armen Stein]

The question now is - how do I apply your code.

I have loaded the J Street Relinker into my Modules of the Front-end
database - but how do I activate its functionality.

Please be patient, and explain (to a dummy) the steps to activate.

Hi Glynn,

Don't worry about the VBA code - you can use it without understanding
it. Later, when you're more familiar with VBA, you can go through it
to see how it works.

Open the ReadMe table in the J Street Access Relinker mdb. Read the
instructions carefully. They tell you how to add a line of code to
your AutoExec macro to automatically check the table links when your
application opens.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

 

[Glynn]

Armen - Thanks for your help.

I have however discovered my problem. After Linking the Databases, I was
doing a 'Compact and Repair' on the Front-end DB - which seems to foul the
whole concept of packaging a Linked system.
If I do not run the C & R routine, the system works fine - installs OK, and
allows me to subsequently enhance or upgrade the system by a simple copying
of an upgraded FE database onto a disk and dispatch to the User to copy.

Another lesson in using a routine that I do not fully understand.

Thanks again for your time and patience.

 

[Armen Stein]

I have however discovered my problem. After Linking the Databases, I was
doing a 'Compact and Repair' on the Front-end DB - which seems to foul the
whole concept of packaging a Linked system.
If I do not run the C & R routine, the system works fine - installs OK, and
allows me to subsequently enhance or upgrade the system by a simple copying
of an upgraded FE database onto a disk and dispatch to the User to copy.

Hmm. I don't see why a compact and repair would have anything to do
with our relinking code. The J Street Access Relinker merely updates
the connection strings for all the linked Access tables. Performing a
C&R should have no effect on them.

But I'm glad it's working for you.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

 

[martin.semerad77]

Hmm. I don't see why a compact and repair would have anything to do

with our relinking code. The J Street Access Relinker merely updates
the connection strings for all the linked Access tables. Performing a
C&R should have no effect on them.

But I'm glad it's working for you.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

Hi,
I use your relinker but I received error 3125 "'T_Items' is not a valid name...." within "Relink" function on the row tdf.RefreshLink. I tried to C & R and the error disappeared but when I tried to chang the BE from the server to the local one, I got the same error (for tables 'T_Items' and '~TMPCLP498911'). All tables named down to 'T_Items' were relinked correctly and the macro stopped on tbl 'T_Items'.
What's wrong?

Regards

Martin