Crash when entering new record

[Linda RQ]

Continued issue from 12/5 post.

I have an access 2003 database in 2000 fileformat. Has been working fine
for 2 years. My IS department recently on Dec 4 upgraded the PCs to Windows
XP Pro from Windows 2000 and this is when the issue started. There are a
million things I could tell you that I have done but I'll just put the
basics in and you can let me know what else you need. After hours of
investigation, I don't think it's a database problem because when I access
the database from a PC with Windows 2000 it works fine. I have a front end
on a network drive and the backend on the same network drive in a different
folder.

My question is, does anyone know of an access issue that would be caused due
to the OS?

When we enter a new patient record on my main form then go to enter the
patient location on a subform which is related by Pt ID we get the error
that Microsoft Office Access has encountered a problem and needs to close.
There is a check box to repair the database and this creates a backup of the
front end. When I send the report to microsoft, nothing comes back but it
could be something my workplace has blocked from returning? Once the
database is closed and reopened we can search for the new patient and then
enter the location. So the workaround for a month has been to enter new
patients in then close the database and reopen to enter the location and all
of the other information.

Let me know what other information is needed.

Thanks,
Linda

 

[Allen Browne]

Linda, I'm not sure what you have already tried, but some suggestions:

1. Make sure each user is opening a *unique* copy of the front end (not
multiple users opening the same MDE.)

2. Keep the path short (< 128 char), e.g. shorten the folder names, and use
only a couple of folders down from the root.

3. Run through the items in this list in order:
Recovery sequence - Standard steps to recover a database
at:
http://allenbrowne.com/recover.html

4. There is a bug where A2002 and A2003 can crash if
LinkMasterFields/LinkChildFields refer to an AccessField rather than a
control. It the subform has no text box for [Pt ID], then:
a) Clear the subform control's LinkMasterFields and LinkChildFields
properties. Save. Close the main form.
b) Open the subform in design view, and add the text box (hidden if you
like.) Save. Close.
c) Open the main form in design view, and enter the LinkMasterFields and
LinkChildFields properties. (Be sure to use the Name of the text box rather
than its Control Source if they differ.)
d) Compact.
This item is #3 under part 2 of this article:
http://allenbrowne.com/ser-25.html

Hope this helps. If you are still stuck, the next stage would be re-creating
this table. Post back if you're stuck.

 

[Linda RQ]

Thanks Allen. I am not sure how to go about making a unique copy for each
user. We can't install anything on the c drives because of security issues.
Would it be better for me to have multiple copies of the front end on the
network drive and have each user assigned to one of them for the day?

I am thinking perhaps #4 may be something to look at, I am not sure what you
mean by "an AccessField rather than a control." I do know I have a hidden
Pt ID field on my subform which is the child.

I went to another hospital tonight and opened a copy of my database from
their windows xp computer (duh I forgot to check which version of Access was
on it and what SP) I'll try to get back there tomorrow or Sunday if the snow
ever stops coming.

Thanks for the links. They look like some interesting reading in a
snowstorm.

Linda

Linda, I'm not sure what you have already tried, but some suggestions:

1. Make sure each user is opening a *unique* copy of the front end (not
multiple users opening the same MDE.)

2. Keep the path short (< 128 char), e.g. shorten the folder names, and
use only a couple of folders down from the root.

3. Run through the items in this list in order:
Recovery sequence - Standard steps to recover a database
at:
http://allenbrowne.com/recover.html

4. There is a bug where A2002 and A2003 can crash if
LinkMasterFields/LinkChildFields refer to an AccessField rather than a
control. It the subform has no text box for [Pt ID], then:
a) Clear the subform control's LinkMasterFields and LinkChildFields
properties. Save. Close the main form.
b) Open the subform in design view, and add the text box (hidden if you
like.) Save. Close.
c) Open the main form in design view, and enter the LinkMasterFields and
LinkChildFields properties. (Be sure to use the Name of the text box
rather than its Control Source if they differ.)
d) Compact.
This item is #3 under part 2 of this article:
http://allenbrowne.com/ser-25.html

Hope this helps. If you are still stuck, the next stage would be
re-creating this table. Post back if you're stuck.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Continued issue from 12/5 post.

I have an access 2003 database in 2000 fileformat. Has been working fine
for 2 years. My IS department recently on Dec 4 upgraded the PCs to
Windows XP Pro from Windows 2000 and this is when the issue started.
There are a million things I could tell you that I have done but I'll
just put the basics in and you can let me know what else you need. After
hours of investigation, I don't think it's a database problem because
when I access the database from a PC with Windows 2000 it works fine. I
have a front end on a network drive and the backend on the same network
drive in a different folder.

My question is, does anyone know of an access issue that would be caused
due to the OS?

When we enter a new patient record on my main form then go to enter the
patient location on a subform which is related by Pt ID we get the error
that Microsoft Office Access has encountered a problem and needs to
close. There is a check box to repair the database and this creates a
backup of the front end. When I send the report to microsoft, nothing
comes back but it could be something my workplace has blocked from
returning? Once the database is closed and reopened we can search for
the new patient and then enter the location. So the workaround for a
month has been to enter new patients in then close the database and
reopen to enter the location and all of the other information.

Let me know what other information is needed.

Thanks,
Linda

 

[Allen Browne]

Responses in-line.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Thanks Allen. I am not sure how to go about making a unique copy for each
user. We can't install anything on the c drives because of security
issues. Would it be better for me to have multiple copies of the front end
on the network drive and have each user assigned to one of them for the
day?

Yes: a separate copy for each user on the network drive would prevent some
mulit-user issues.

I am thinking perhaps #4 may be something to look at, I am not sure what
you mean by "an AccessField rather than a control." I do know I have a
hidden Pt ID field on my subform which is the child.

Hidden control is fine. (An AccessField is the object type if you refer to a
field in the form's recordset directly.)