Access Data stored in SQL Server
I'm currently working on a project to convert our Access Apps to store the table data in SQL Server.
Using SSMA to migrate the data results in the foreign keys and Look-ups work as expected in Access when completed. However, if I import & link directly from SQL Server back to Access, the foreign key look-ups do not work.
The only difference I can determine in the links is, the ones SSMA created do not specify a DSN and the ones I manually created do.
I'm hopefully someone might have run into this in the past and might have some insight.
We are migrating from Access 2013 to SQL Server 2012.
sql-server ms-access ssma
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm currently working on a project to convert our Access Apps to store the table data in SQL Server.
Using SSMA to migrate the data results in the foreign keys and Look-ups work as expected in Access when completed. However, if I import & link directly from SQL Server back to Access, the foreign key look-ups do not work.
The only difference I can determine in the links is, the ones SSMA created do not specify a DSN and the ones I manually created do.
I'm hopefully someone might have run into this in the past and might have some insight.
We are migrating from Access 2013 to SQL Server 2012.
sql-server ms-access ssma
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm currently working on a project to convert our Access Apps to store the table data in SQL Server.
Using SSMA to migrate the data results in the foreign keys and Look-ups work as expected in Access when completed. However, if I import & link directly from SQL Server back to Access, the foreign key look-ups do not work.
The only difference I can determine in the links is, the ones SSMA created do not specify a DSN and the ones I manually created do.
I'm hopefully someone might have run into this in the past and might have some insight.
We are migrating from Access 2013 to SQL Server 2012.
sql-server ms-access ssma
I'm currently working on a project to convert our Access Apps to store the table data in SQL Server.
Using SSMA to migrate the data results in the foreign keys and Look-ups work as expected in Access when completed. However, if I import & link directly from SQL Server back to Access, the foreign key look-ups do not work.
The only difference I can determine in the links is, the ones SSMA created do not specify a DSN and the ones I manually created do.
I'm hopefully someone might have run into this in the past and might have some insight.
We are migrating from Access 2013 to SQL Server 2012.
sql-server ms-access ssma
sql-server ms-access ssma
asked Jun 11 '15 at 15:24
Bryan SmithBryan Smith
142
142
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I finally determined the lookups have the be setup in Access, they won't automatically be created when attaching a sql server table as a link.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f103809%2faccess-data-stored-in-sql-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I finally determined the lookups have the be setup in Access, they won't automatically be created when attaching a sql server table as a link.
add a comment |
I finally determined the lookups have the be setup in Access, they won't automatically be created when attaching a sql server table as a link.
add a comment |
I finally determined the lookups have the be setup in Access, they won't automatically be created when attaching a sql server table as a link.
I finally determined the lookups have the be setup in Access, they won't automatically be created when attaching a sql server table as a link.
answered Jun 12 '15 at 11:39
Bryan SmithBryan Smith
142
142
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f103809%2faccess-data-stored-in-sql-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown