AFAIK all the SQL Server access is done using ODBC -- the
Access DB just creates what I assume are proxy tables,
that when called retrieve the data over ODBC.

I've not coded any of the DB access stuff manually using
ADO, it just uses Access' built in data-binding etc.

I figured it was something to do with the record locking.
Just not sure what causes it or how to fix it :)


-----Original Message-----
This is a question more so for the Access ADO programming
newsgroup
(microsoft.public.access.modulesdaovba.ado) since SQL
Server 2000 doesn't
take DAO coding. I not really the best person to ask
about the ADO stuff,
but I suspect you have something going on with your ADO
code that is
preventing you from editting records such as the type of
record level
locking may be interferring with it. Another thing to
consider, what are
the set permissions on the table(s) that you are adding
records to. Does it
allow you to add, but not change like transactional
tables?

--
Ronald R. Dodge, Jr.
Production Statistician
Master MOUS 2000
"Paul Ingles" wrote in
message
...
I have an MS Access based front end to an SQL Server
database. If I create records using the Access client
all
works fine, however, I have an old MS Access DB that I'm
trying to take records from.

I've tried doing it numerous ways, but the only way that
seems to work is by using an INSERT..SELECT statement
within the old Access DB that adds the records. However,
if I then use Access to edit a record it then pops up an
error box saying that the record may have been changed
and
my changes cannot be saved.

I assume this is something to do with the way records
are
timestamped to warn against consistency problems.

Anyway, I can't figure out how to sort this. I need to
add
old records, but every method I've tried means I can't
edit them afterwards. I'm using SQL Server 2000 and
Microsoft Access 2000 with MDAC 2.7 SP1.

Any suggestions would be appreciated.

Regards,
Paul



.