Add record button not working

[Guest]

Please excuse the cross-newsgroup post but I'm in a bit of a time crunch

I have a form that users use to enter data into a table. During development, all was well; it worked perfectly. When I upsized it to my local instance of SQL Server, all was well. In moving it into the production phase, I moved it up to a SQL Server and now it's behaving differently. The form 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 on the form 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

I have since noticed that there is no key field in one of the upsized table. Could this be the problem/reason
tia
JMorrel

 

[Brendan Reynolds]

The absence of a key field may very well be the problem. Any ODBC-linked
table that has no unique index or constraint will be treated as read-only.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.

Please excuse the cross-newsgroup post but I'm in a bit of a time crunch.

I have a form that users use to enter data into a table. During

development, all was well; it worked perfectly. When I upsized it to my
local instance of SQL Server, all was well. In moving it into the
production phase, I moved it up to a SQL Server and now it's behaving
differently. The form 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 on the form 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.

I have since noticed that there is no key field in one of the upsized

table. Could this be the problem/reason?

 

[Roger Carlson]

Yes. In SQL Server, you MUST have a unique field defined in order for the
table to be updatable. This could account for both of the errors mentioned.

--
--Roger Carlson
www.rogersaccesslibrary.com
Reply to: Roger dot Carlson at Spectrum-Health dot Org

Please excuse the cross-newsgroup post but I'm in a bit of a time crunch.

I have a form that users use to enter data into a table. During

development, all was well; it worked perfectly. When I upsized it to my
local instance of SQL Server, all was well. In moving it into the
production phase, I moved it up to a SQL Server and now it's behaving
differently. The form 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 on the form 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.

I have since noticed that there is no key field in one of the upsized

table. Could this be the problem/reason?

 

[Douglas J. Steele]

But you haven't cross-posted. Crossposting means that you posted one
message, and it was copied to more than one newsgroup. Most newsreaders will
only see the message once, and all responses will be available together,
regardless of which newsgroup the responder was actually reading at the
time.

If you sent this to other newsgroups, you must have multiposted. In other
words, you went to newsgroup A and posted the message, went to newsgroup B
and posted the same message and so on.

Reasonable crossposting is fine. Multiposting isn't. It puts more strain on
the servers, and it's a nuisance to others who end up seeing your post
multiple times or, worse, spend time trying to answer your post, only to
discover someone has already provided you with the answer in one of the
other newsgroups to which you posted.

--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)

Please excuse the cross-newsgroup post but I'm in a bit of a time crunch.

I have a form that users use to enter data into a table. During

development, all was well; it worked perfectly. When I upsized it to my
local instance of SQL Server, all was well. In moving it into the
production phase, I moved it up to a SQL Server and now it's behaving
differently. The form 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 on the form 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.

I have since noticed that there is no key field in one of the upsized

table. Could this be the problem/reason?