Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

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

Posted on 2011-09-23
8
Medium Priority
?
295 Views
Last Modified: 2012-05-12
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
Comment
Question by:ironpen45
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
8 Comments
 

Author Comment

by:ironpen45
ID: 36589170
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
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 36591029
>>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
 

Author Comment

by:ironpen45
ID: 36591116
>>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
Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 36592776
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
 

Author Comment

by:ironpen45
ID: 36599112
>>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
 

Accepted Solution

by:
ironpen45 earned 0 total points
ID: 36599471
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
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 36654771
>>found the solution: <<
Excellent! Now please close the question.
0
 

Author Closing Comment

by:ironpen45
ID: 37130065
because it works
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

AutoNumbers should increment automatically, without duplicates.  But sometimes something goes wrong, and the next AutoNumber value is a duplicate.  This article shows how to recover from this problem.
In Part II of this series, I will discuss how to identify all open instances of Excel and enumerate the workbooks, spreadsheets, and named ranges within each of those instances.
In Microsoft Access, learn how to “cascade” or have the displayed data of one combo control depend upon what’s entered in another. Base the dependent combo on a query for its row source: Add a reference to the first combo on the form as criteria i…
With Microsoft Access, learn how to specify relationships between tables and set various options on the relationship. Add the tables: Create the relationship: Decide if you’re going to set referential integrity: Decide if you want cascade upda…

704 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question