Add Record Command Button not working

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a form that users use to enter data into a table. During development, all was well; it worked perfectly. I moved it up to a SQL Server and now it's behaving differently. The for now does not have an "add record button" on the record/status bar at the bottom of the form (it's there, just grayed out). What would cause this? Anyone?

I also have a command button that I created to add a record (via the wizard) and it gives the error, "You can't go to the specified record." The problem is related, but I can't figure it out. The standard tool bar "add a record" button is grayed out

tia
JMorrell
 
Hey, I'm having the same problem in Access 2000/2002, I've been looking at
it for days.
I also have a command button to add records and have not modified its
underlying code. It used to work, but now it doesn't.
First I get the ...can't go to specified record message. Then when I click
it again I get the record add form, but all the controls are locked. I'm
not using SQL Server, just the normal Access database engine.
I thought the code might be corrupted so a imported the code into a new db,
but it still behaved the same way. I've traced the code execution and
monitored the form & control properties, but all looks normal. go figure!

Add my voice to the cry for help on this one.
thanks
Jim Shaw

JMorrell said:
I have a form that users use to enter data into a table. During
development, all was well; it worked perfectly. I moved it up to a SQL
Server and now it's behaving differently. The for now does not have an "add
record button" on the record/status bar at the bottom of the form (it's
there, just grayed out). What would cause this? Anyone?
I also have a command button that I created to add a record (via the
wizard) and it gives the error, "You can't go to the specified record." The
problem is related, but I can't figure it out. The standard tool bar "add a
record" button is grayed out.
 
Problem fixed. Read the following from Brandan Reynolds

.... Any ODBC-linked table that has no unique index or constraint will be treated as read-only

I created a new field (a key field) in the table that was causing the problem. Moved it over to the SQL Server, cleaned it up, relinked the table, refreshed the link. All is well when one knows what's going on

Hope this helps you in your problem
JMorrell
 
Back
Top