Re: Duplicating data in continuous subform linked to SQL



The problem ended up being a primary key.... Not sure how to answer your
questions properly; however, I am using an Access front end with ODBC linked
tables to a SQL 2008 DB that was upsized with Access 2003 to SQL 2005 then
backed up and restored int SQL 2008. Everything seems to be working properly
after I added primary keys to all the tables that did not have them.

Sylvain Lafontaine wrote:
The first thing would be to tell us if you are using an MDB or ACCDB file
with ODBC linked tables or an ADP project connected to a SQL-Server. It's
not only because this group is about ADP but also because these two products
work entirely differently.

As to your problem, it's looks to me that either the upsized table don't
have a primary key or that Access has some trouble finding it or using it;
for example because you would have a composite primary key (two or more
fields) or because you have another unique index on the table and Access is
using this second unique index as the primary key.

Take also a look at the UniqueTable property of the subform (or something
like that). Using the wrong table as the UniqueTable might give you this
strange behavior.

In all cases, you should take a look with the SQL-Server Profiler to see
what's going on; ie., to see what Access is doing against the SQL-Server.

Ok, I am working on upsizing a FE/BE DB that I have to a SQL 200X BE. I
did
[quoted text clipped - 17 lines]

Thanks in advance for any help.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-adp-sqlserver/200809/1

.



Relevant Pages

  • Re: Duplicating data in continuous subform linked to SQL
    ... have a primary key or that Access has some trouble finding it or using it; ... using this second unique index as the primary key. ... you should take a look with the SQL-Server Profiler to see ... I have a main form that has multiple subforms under tabs... ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Whats Informix thinking or Idea
    ... SQL and the way Informix works underneath. ... I guess the choice for the developers was either not to allow the standard SQL above and force explicit creation of a unique index before a primary key could be created, or allow the SQL above and create an index implicitly. ...
    (comp.databases.informix)
  • Re: Unique and non unique index
    ... The Non unique index are required to be created for faster data ... Copyright 1982, 2005, Oracle. ... SQL> create table t ( ... PRIMARY KEY (col1) ...
    (comp.databases.oracle.misc)
  • Re: Not accepting new records..?
    ... When did you add the primary key, ... design view of the SQL table, do you notice a primary key? ... > But If I then export the tables to SQL-server and link them back to Access ...
    (microsoft.public.access.queries)
  • Re: access-SQL ODBC link
    ... You need to create a primary key or unique index on any SQLS tables ... >> I am using trusted windows user connection to SQL ... >> able to modify data in tables through SQL Enterprise ...
    (microsoft.public.sqlserver.odbc)