[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 300
  • Last Modified:

write conflicts & Jet engine error messages on some records and not on others

i've come across a problem on a linked table (from a SQL server 2k backend) in an MDB file.

for this particular table, the majority of the records can be edited, deleted and i can also add new ones as well. however, for a very small subset, i cannot with the write conflict and "Jet database stopped" messages.

i deleted and relinked the table, i checked the permissions on the SQL server, and made sure there was a unique identity on the table as well.

the interesting fact is that the records are uneditable and undeletable were created via a form, and each time each was created, the write conflict error would pop up, but the record would still be saved (each uneditable and undeletable).

any ideas? thanks!
0
ironpen45
Asked:
ironpen45
  • 5
  • 3
1 Solution
 
ironpen45Author Commented:
update: if i copy an entire row and paste it on the table, i'm able to delete and edit this newly entered record. however, if i manually enter data in each field (column) from left to right, then the record is uneditable/undeletable in access. i can still edit and delete in SQL.
0
 
Anthony PerkinsCommented:
>>and made sure there was a unique identity on the table as well.<<
An IDENTITY column does not mean that it is unique.  More important is:  Do you have a Primary Key on the table?

0
 
ironpen45Author Commented:
>>An IDENTITY column does not mean that it is unique.  More important is:  Do you have a Primary Key on the table?<<

yes, it also has a primary key which happens to be have an IDENTITY property.

another observation: i can remove those undeletable records with a delete query.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
Anthony PerkinsCommented:
If you have defined a Primary Key on the column with an IDENTITY attribute, then I have no idea what could be the problem.
0
 
ironpen45Author Commented:
>>If you have defined a Primary Key on the column with an IDENTITY attribute, then I have no idea what could be the problem. <<

i created a new MDB, linked the table in question and noticed the same thing (able to edit/delete older records, but not newer records).

generally, one would expected the same behavior for all records in a given table, but not some (newer) records and yes for the majority (older) records.

would constraints be an issue?

i think i've exhausted my search. please help!
0
 
ironpen45Author Commented:
found the solution: http://support.microsoft.com/kb/280730.

the problem was a bunch of bit and float type fields with null values. what was confounding was the older records has data in them, allowing me to edit/delete whereas the newer ones had no default value and allowed nulls.

just added a date/time stamp field with timestamp and works like a charm.
0
 
Anthony PerkinsCommented:
>>found the solution: <<
Excellent! Now please close the question.
0
 
ironpen45Author Commented:
because it works
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now