A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

#Deleted Error



 
 
Thread Tools Display Modes
  #1  
Old August 10th, 2006, 09:55 PM posted to microsoft.public.access.tablesdbdesign
maura
external usenet poster
 
Posts: 37
Default #Deleted Error

I have a split database, that 3 people utilized... one of the fields (called
Updates) is a memo field, where we can mantain notes on an account. I am not
sure if two people had the same record open at the same time (but I believe
this to be the case), and each tried to modify the record, specifically the
Updates field, but now we have #Deleted instead of the notes. I went to the
back-up and copied the notes, but the #Deleted won't let me paste the notes
back into the field.

I have read another posting where it says: Set your form's Allow Deletions
property to NO if they aren't supposed to be able to delete records. (data
tab of form properties), but do you do this for the field itself or do you
set the properties for the form itself? How will this effect things?

Should I have set something else when I split the database to make sure no
two people could change a record at the same time?

Any suggestions would be Greatly Apprecitated!
Maura

  #2  
Old August 11th, 2006, 04:36 AM posted to microsoft.public.access.tablesdbdesign
Allen Browne
external usenet poster
 
Posts: 11,706
Default #Deleted Error

Sounds like something has gone wrong with this particular record.

Try opening the table in design view, and deleting that one record. If
Access won't let you delete it, get Access to rebuild the table for you.
Follow the steps for Symptom #3 in this article:
Recovering from corruption
at:
http://allenbrowne.com/ser-47.html

The corruption is probably nothing that you did; it is something Access did.
Because of the amount of data that gets stored in a memo, Access does not
store it in line with the rest if the table data, but stores the memos in
another location. If the pointer goes bad, it is as if Access has forgotten
where to find the memo again. This is not common, but it does happen.

There's a long list of things that you can do to help prevent this kind of
problem he
Preventing Corruption
at:
http://allenbrowne.com/ser-25.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"maura" wrote in message
...
I have a split database, that 3 people utilized... one of the fields
(called
Updates) is a memo field, where we can mantain notes on an account. I am
not
sure if two people had the same record open at the same time (but I
believe
this to be the case), and each tried to modify the record, specifically
the
Updates field, but now we have #Deleted instead of the notes. I went to
the
back-up and copied the notes, but the #Deleted won't let me paste the
notes
back into the field.

I have read another posting where it says: Set your form's Allow Deletions
property to NO if they aren't supposed to be able to delete records. (data
tab of form properties), but do you do this for the field itself or do you
set the properties for the form itself? How will this effect things?

Should I have set something else when I split the database to make sure no
two people could change a record at the same time?

Any suggestions would be Greatly Apprecitated!
Maura



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 02:06 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.