Re: Changing linked SQL Server tables in code
- From: "Rick Brandt" <rickbrandt2@xxxxxxxxxxx>
- Date: Mon, 23 Jun 2008 18:30:18 -0500
brucedodds@xxxxxxxxxxx wrote:
I've inherited an A2003 application with linked SQL Server 2000 tables
in the back end, using the Microsoft SQL Server ODBC driver.
We've set up a test SQL Server database. I'd like to automate the
process of relinking the application to test/prod.
I've found some code examples here of relinking ODBC back ends to
different databases, but they involve deleting the table before
relinking. My concern is that the primary key information for the
tables will be lost when the table is deleted. A linked ODBC table
can't be updated unless it has a primary key defined.
If the server table has a PK or unique index this won't happen.
If anyone can provide information on how to change ODBC linked tables
in code, while maintaining the primary key, I'd appreciate it.
Are you using DSNless connections? If not I have never had any problems
just changing the DSN and not even touching the Access app.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
.
- Follow-Ups:
- Re: Changing linked SQL Server tables in code
- From: brucedodds
- Re: Changing linked SQL Server tables in code
- References:
- Changing linked SQL Server tables in code
- From: brucedodds
- Changing linked SQL Server tables in code
- Prev by Date: Re: linked tables access - sql
- Next by Date: Re: Changing linked SQL Server tables in code
- Previous by thread: Re: Changing linked SQL Server tables in code
- Next by thread: Re: Changing linked SQL Server tables in code
- Index(es):
Relevant Pages
|