asked on Creating a DSN-less, updatable SQL Server linked table in Access 2007
In Access 2007, I've created a DSN-less connection to a SQL Server 2008 R2 table, to create a linked table which I've dropped into an Access form. I followed this MS link:
http://support.microsoft.com/kb/892490
In VBA, I used the Form_Open event to call "AttachDSNLessTable" as outline in the KB article.
Q1: I see "Recordset is not updateable", and it won't let me edit the recordset. I'm assuming it doesn't maintain connection to the SQL table. How do I change this so I can add/edit/delete records in this linked table (and thus have them automatically propogate to the SQL table)?
Q2: From VBA, I'd like to be able to update this linked table in certain spots in a procedure. How do I do so?
I suspect these 2 questions are related. Thanks.
http://support.microsoft.com/kb/892490
In VBA, I used the Form_Open event to call "AttachDSNLessTable" as outline in the KB article.
Q1: I see "Recordset is not updateable", and it won't let me edit the recordset. I'm assuming it doesn't maintain connection to the SQL table. How do I change this so I can add/edit/delete records in this linked table (and thus have them automatically propogate to the SQL table)?
Q2: From VBA, I'd like to be able to update this linked table in certain spots in a procedure. How do I do so?
I suspect these 2 questions are related. Thanks.
Microsoft AccessVB ScriptMicrosoft Office
Last Comment
Gustav Brock
ASKER
There is a timestamp field, but the records are not necessarily unique on that field (it's an "edited" field). How does that affect this?
I'm using ADO currently... How does this differ from DAO in this case?
I'm using ADO currently... How does this differ from DAO in this case?
You will also need a primary key in the table in order to edit it from Access.
ASKER
Thanks, fyed. That's probably it ... I didn't create the table :-P
ASKER
I found the problem: Access can't handle bigint datatypes, which is what the primary key was identified with.
That takes care of Q1.
I'm still having an issue with Q2: namely, I'd like to be able to update the linked table (the same as going through the Linked Table Manager, selecting the linked table, and updating manually), but through VBA code. I've come across dozens of blogs and nothing seems to update.
I'd like this so if Access has been open for some time, the user can click a Refresh button to ensure that what they see on screen is true to the SQL table.
That takes care of Q1.
I'm still having an issue with Q2: namely, I'd like to be able to update the linked table (the same as going through the Linked Table Manager, selecting the linked table, and updating manually), but through VBA code. I've come across dozens of blogs and nothing seems to update.
I'd like this so if Access has been open for some time, the user can click a Refresh button to ensure that what they see on screen is true to the SQL table.
For that you only need to requery the recordset of the form the user is watching.
Relinking is only needed when schema changes (adding/modifying fields etc.) have taken place.
/gustav
Relinking is only needed when schema changes (adding/modifying fields etc.) have taken place.
/gustav
ASKER
Gustav,
Any idea what that syntax would look like? I ask because I tried a few methods, one of which used a ".RefreshLink" or ".Refresh"(?) and the table didn't update when an underlying record change had happened.
Any idea what that syntax would look like? I ask because I tried a few methods, one of which used a ".RefreshLink" or ".Refresh"(?) and the table didn't update when an underlying record change had happened.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Q2: Like any other recordset using DAO.
/gustav