B
Bonnie
Hi there. Using A02 on XP. Not a prof-programmer, but self
taught Access fan. Have created/maintained MDB files in
multiuser environment and now have user level security
with some pretty good group permissions, I disable the
shift/bypass key, use custom toolbars, have a front
end/back end design, use event procedures and macros,
learning VB, so I feel they run pretty well. As I learn
new techniques and methods, I integrate them into my DB's
(most were created in A97). BUT, I do have one DB (highest
usage file) that does crash a few times a year with the
#Deleted problem. I've narrowed it down to this: first
person has a record open and goes to second person to
discuss the paperwork, the second person opens the same
record and thinking all is complete, appends the record to
an historical table, then the first person (with focus
still on that deleted/appended record) having returned to
their desk, makes an edit on the screen and then tries to
close the form. The record has been appended to another
table but where it should have been deleted from the
active table, it is now a row of #Deleted, #Deleted, etc.
fields and the forms lock up and there's a 'bad' record in
the table that must be addressed. Can only do that by
copying the structure (no data) and then appending all the
records before and after the 'bad' one. Delete old table
and rename new one, reset relationships, blah, blah. Whew!
Am trying to decide if MDE's would be more stable or less
likely to allow that to happen. Or is there a better way
to prevent the #Deleted problem?
I also have a module I like to open sometimes to see a
list of current users and that won't work in an MDE. What
would my alternative for that be in an MDE file so I can
still see a list of current users? Can I use a form to
display the results of the module?
Sorry to wax long. Would appreciate any help or advice.
Thanks in advance for any replies. (If it weren't for you
guys in the newsgroups, many folks like me would still be
floundering. You provide the learning gap so the steps in
the procedure manuals make better sense. Thanks alot.)
taught Access fan. Have created/maintained MDB files in
multiuser environment and now have user level security
with some pretty good group permissions, I disable the
shift/bypass key, use custom toolbars, have a front
end/back end design, use event procedures and macros,
learning VB, so I feel they run pretty well. As I learn
new techniques and methods, I integrate them into my DB's
(most were created in A97). BUT, I do have one DB (highest
usage file) that does crash a few times a year with the
#Deleted problem. I've narrowed it down to this: first
person has a record open and goes to second person to
discuss the paperwork, the second person opens the same
record and thinking all is complete, appends the record to
an historical table, then the first person (with focus
still on that deleted/appended record) having returned to
their desk, makes an edit on the screen and then tries to
close the form. The record has been appended to another
table but where it should have been deleted from the
active table, it is now a row of #Deleted, #Deleted, etc.
fields and the forms lock up and there's a 'bad' record in
the table that must be addressed. Can only do that by
copying the structure (no data) and then appending all the
records before and after the 'bad' one. Delete old table
and rename new one, reset relationships, blah, blah. Whew!
Am trying to decide if MDE's would be more stable or less
likely to allow that to happen. Or is there a better way
to prevent the #Deleted problem?
I also have a module I like to open sometimes to see a
list of current users and that won't work in an MDE. What
would my alternative for that be in an MDE file so I can
still see a list of current users? Can I use a form to
display the results of the module?
Sorry to wax long. Would appreciate any help or advice.
Thanks in advance for any replies. (If it weren't for you
guys in the newsgroups, many folks like me would still be
floundering. You provide the learning gap so the steps in
the procedure manuals make better sense. Thanks alot.)