[AccessD] Weird problem

Yep, I have done this many times.  I always use an int (which is a long in in SQL Server) 
autoincrement and it is marked as a PK.  AFAICT that's not the problem.

John W. Colby
Colby Consulting

Reality is what refuses to go away
when you do not believe in it

On 1/10/2012 5:57 PM, Darryl Collins wrote:
> John,
>
> My first suspect would be primary keys.  You need to
>
> 1: have a primary key linked to Access from SQL server
> 2: the key needs to be dimmed a specific type (BigInt?) - can't recall the exact type required - sorry.
>
> Cheers
> Darryl.
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Wednesday, 11 January 2012 9:49 AM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] Weird problem
>
> I have a FE recently moved to SQL Server.  Bound main form, bound child form.  I entered a record in the main form, entered a record in the child form.  Tried to modify the record in the main form and it gives an error "the data has changed" and refuses to allow me to change the data.  I can change it directly in the tables in SQL Server.  I cannot modify the record directly in the (linked) table in the FE.
>
> I could create the record, but not modify the record.  I can modify any other record in the table, just not the one I created.
>
> No idea why not.
>
> --
> John W. Colby
> Colby Consulting
>
> Reality is what refuses to go away
> when you do not believe in it
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
>