G
Guest
I had an Access 2000 data project with a SQL Server 2000 backend. I had a
form bound to a stored procedure. My Unique Table property was set and my
Resync Command was a SQL Statement "Select * from Unique_Table where
PrimaryKey=?". I had an add new record button on my form that executed
"DoCmd.GoToRecord , , acNewRec". This setup worked perfect in Access 2000.
I converted my front-end to Access 2003 and this no longer works. I can only
hit the add new record button once after that I get multiple errors including
Can't find specified records. I've tried using a paramatized stored
procedure for the resync command and followed the steps given by Sylvain
Lafontaine in earlier postings to no avail. I'm now worried that my only
solution would be to create an unbound form and use an ADO Recordset to
manipulate the data. This forms has a large amount of data and fields and
would be a huge undertaking to recreate that way. Any help would be greatly
appreciated.
Thanks,
Keith
form bound to a stored procedure. My Unique Table property was set and my
Resync Command was a SQL Statement "Select * from Unique_Table where
PrimaryKey=?". I had an add new record button on my form that executed
"DoCmd.GoToRecord , , acNewRec". This setup worked perfect in Access 2000.
I converted my front-end to Access 2003 and this no longer works. I can only
hit the add new record button once after that I get multiple errors including
Can't find specified records. I've tried using a paramatized stored
procedure for the resync command and followed the steps given by Sylvain
Lafontaine in earlier postings to no avail. I'm now worried that my only
solution would be to create an unbound form and use an ADO Recordset to
manipulate the data. This forms has a large amount of data and fields and
would be a huge undertaking to recreate that way. Any help would be greatly
appreciated.
Thanks,
Keith