I've encountered the same thing - defining a bit column in
a SQL table and not specifying a default causes headaches. You should
specify a default, but you also need to go back and flip the values in the
existing records to true or false - they're apparently null by
default.
You might to a bulk SQL update that sets your bit value to
0 where it is null.
Tom Oakes From: AccessDevelopers@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Lava Boggavarapu Sent: Friday, January 20, 2006 7:01 AM To: AccessDevelopers@yahoogroups.com Subject: RE: [AccessDevelopers] Record Lock on SQL Do you have any fields connected to a bit type columns in the DB?
I encountered this problem long ago and the culprit was the bit type column. If you do have one, try setting a default value to it.
-----Original
Message-----
I am connected to a SQL backend. I can add
a record just fine but if I The information contained in this message and any attachments (the "Message") is intended for specific individual(s), and may be confidential or proprietary. If you are not the intended recipient, please notify the sender immediately, delete this Message and do not disclose. Messages are not secure or error free and can contain viruses and the sender is not liable for any of these occurrences. The sender reserves the right to monitor, record and retain Messages. Please zip all files prior to uploading to Files section.
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
- [AccessDevelopers] Record Lock on SQL accessrider
- Re: [AccessDevelopers] Record Lock on SQL hal_mcgee
- RE: [AccessDevelopers] Record Lock on SQL Lava Boggavarapu
- RE: [AccessDevelopers] Record Lock on SQL Tom Oakes
- RE: [AccessDevelopers] Record Lock on SQL Tom Oakes