Linked Table Properties - using ODBC trying to rmv DATABASE NAME e

[Guest]

In the past I could fool the system and reset the linked table properties by
modifying the property for a particular row and then saving the application.
Although it would not allow me to change the property at the table property
level.

With 2003 I cannot do this.

The reason for doing this is due to the fact that I do not want to bind i.e.
force the table to be always linked to a specific database. I would like the
DSN to determine the database that it will be linked to.

Reason: So that I can switch the database by repointing the DSN and not
having to deal with the application. It also causes my relink to fail when
it cannot find the database.

Example:

I link to DSN:Onyx and my database for Staging id Onyx_STG, for development
is Onyx_DEV and Onyx_Dev is used for development.

With the current version when I link a table to the SQL database the
properties are: ODBC;DSN=ONYX;APP=Microsoft Office
2003;WSID=SYSPRO1800;DATABASE=Onyx_DEV;Network=DBMSSOCN;TABLE=dbo.company

However, when I move it to my staging machine, the database Onyx_Dev is no
longer there and it fails. In the past I could modify the connect string
such that it would only read:
ODBC;DSN=ONYX;UID=onyx1;TABLE=dbo.company

Now in my application my old linked tables still work although they have
these old settings. However my new tables will not work and my relink script
fails. When I move the applcation from one region to another.

Is there a way for me to reset the properties, like what I had done in the
past?

Derrick

 

[Tim Ferguson]

However, when I move it to my staging machine, the database Onyx_Dev
is no longer there and it fails. In the past I could modify the
connect string such that it would only read:
ODBC;DSN=ONYX;UID=onyx1;TABLE=dbo.company

Now in my application my old linked tables still work although they
have these old settings. However my new tables will not work and my
relink script fails. When I move the applcation from one region to
another.

You don't give much detail of _how_ you are regenerating the link. The
details of what has to go in the .Connect property of the Tabledef object
are outlined in Access (DAO) help, and will be given more specifically in
the provider's help file (for SQL Server, probably look in the Books On
Line file).

After resetting the .Connect property, remember to call the .RefreshLink
method -- that is the one that actually goes out to find the data.

You haven't put any password string in the Connect string you posted: I
guess you are doing so in Real Life.

HTH


Tim F

 

[Guest]

Dear Tim,

I am asking about the MS access interface. It does not allow me to change
the connect parms after creating a link table. I do not understand why this
is so. In the earlier versions, I could do this.

The relink is executed by calling the refreshLink method. I have no
problems when in the past I just set the parms with "ODBC;DSN=ONYX" without
any passwords or users etc. This is what I am trying to get at. The current
2000-2003 versions puts in the other parms such as database= etc. I do not
think that it needs it internally, as the database should be extracted from
the DSN. The DSN setup also has the appropriate signon and password. It
does not make sense, if we need to set up all this info will it override the
current DSN settings on the computer?

This was working fine in the old versions where i had just ODBC and the DSN;
I tried resetting the connect string in the refreshLink method but it does
not reset the Link Table for some reason. Is there antoher method I have to
call first.

 

[Tim Ferguson]

The relink is executed by calling the refreshLink method. I have no
problems when in the past I just set the parms with "ODBC;DSN=ONYX"
without any passwords or users etc. This is what I am trying to get
at. The current 2000-2003 versions puts in the other parms such as
database= etc. I do not think that it needs it internally, as the
database should be extracted from the DSN.

Aha: I see the problem now, although I'm afraid I don't have much idea
about the solution.

It might be worth asking again in one of the odbc groups -- try
m.p.access.odbcclientsvr perhaps?

It's not what you want, but it might not be too hard to write the new
connect details into the database File Properties, and have some code read
them back and re-establish the link in full.

Best of luck


Tim F

 

[Guest]

Dear Tim,

Are you with Microsoft? How do I raise this issue with microsoft's MS
Access development team?

DPC

 

[Tim Ferguson]

Are you with Microsoft? How do I raise this issue with microsoft's MS
Access development team?

No I'm not: I'm just another newsgroup reader. Some of the MVPs have access
to the development teams.

There should be a feedback form in the MSDE website.

Best wishes


Tim F

 

[Guest]

Tim,

Thanks for you help.

I will look for the MSDE website. When I joined MSDN and the MS partners, I
was told that this site would be monitored and answered by MS pers. Do I
have the wrong site? Is there another site that I can get direct support
from MS personnel for free. As this issue is to solve the problem for a
client with whom I am consulting.

 

[Tim Ferguson]

I will look for the MSDE website. When I joined MSDN and the MS
partners, I was told that this site would be monitored and answered
by MS pers. Do I have the wrong site?

There are occasional postings by MS support themselves, but it's not
regular and I don't think I've seen any for a while.

Is there another site that I
can get direct support from MS personnel for free.

Tee hee... The knowledge base carries a huge amount of stuff about things
you didn't even know you had to know about, but I find it really hard to
search or navigate. Sorry if you have already tried this, but starting at
<http://msdn.microsoft.com/> and searching for "ODBC RefreshLink" produces
several pages of hits.

Best of luck


Tim F

 

[Douglas J. Steele]

Actually, I believe he's talking about the "concierge" service (or have they
changed the name?) MSDN subscribers are supposed to receive.

Are you posting using the same passport that's associated with your MSDN
subscription?

 

[Guest]

Yes I am

Actually, I believe he's talking about the "concierge" service (or have they
changed the name?) MSDN subscribers are supposed to receive.

Are you posting using the same passport that's associated with your MSDN
subscription?