Hi, this is my second problem.
To save you digging back to see what Ive done, it was basically an upgrade
from a simple Access 97 database straight to 2003.

The original issues I was getting are all to do with the db crashing at
random times, usually when leaving or entering a page. Adding the lates
service pack has fixed all but one issue.

I have one form, that needs to call DoCmd.Close acForm, "Appeals",
acSavePrompt.

When this is called, the application crashes, and drops straight to the
"Tell Microsoft " Error message window, without even displaying any error
message information. On a single machine I have removed all the service
packs, and this issue does not occur. The people in that office want to keep
SP2 and the patches on their PC's, so is there a workround to this, other
than the "Switch it all to MySQL" that the office junior keeps helpfully
suggesting...

The Whole piece of code for the close down routine is

Private Sub Close_Click()
On Error GoTo Close_err
DoCmd.Close acForm, "Appeals", acSavePrompt
Close_exit:
Exit Sub
Close_err:
MsgBox Err.Description
Resume
Close_exit
End Sub

Thanks in advance for any suggestions or tweaks

Did you use Debug, Compile to see if it finds any errors in any code?
Follow that with Save, and then Compact and Repair.

I'm not sure if you realize that the acSavePrompt refers only to saving
design changes, not data. Do you really need this in a production
application? Try removing it.


--
Joan Wild
Microsoft Access MVP

John Smith wrote:
> Hi, this is my second problem.
> To save you digging back to see what Ive done, it was basically an
> upgrade from a simple Access 97 database straight to 2003.
>
> The original issues I was getting are all to do with the db crashing
> at random times, usually when leaving or entering a page. Adding the
> lates service pack has fixed all but one issue.
>
> I have one form, that needs to call DoCmd.Close acForm, "Appeals",
> acSavePrompt.
>
> When this is called, the application crashes, and drops straight to
> the "Tell Microsoft " Error message window, without even displaying
> any error message information. On a single machine I have removed all
> the service packs, and this issue does not occur. The people in that
> office want to keep SP2 and the patches on their PC's, so is there a
> workround to this, other than the "Switch it all to MySQL" that the
> office junior keeps helpfully suggesting...
>
> The Whole piece of code for the close down routine is
>
> Private Sub Close_Click()
> On Error GoTo Close_err
> DoCmd.Close acForm, "Appeals", acSavePrompt
> Close_exit:
> Exit Sub
> Close_err:
> MsgBox Err.Description
> Resume
> Close_exit
> End Sub
>
> Thanks in advance for any suggestions or tweaks

John Smith wrote:
> I have one form, that needs to call DoCmd.Close acForm, "Appeals",
> acSavePrompt.

As Joan advised, you probably don't need to save the form's design every time
the form closes. But do all the users have a copy of the front end on their
desktops? This would be a bigger issue if users were sharing the front end
on the server.

> When this is called, the application crashes

As Joan advised, make sure the code is compiled *before* you run code.

> On a single machine I have removed all the service
> packs, and this issue does not occur.

Put the service packs back on, at least through Office 2003 SP1. Access 2003
without the first service pack is less stable.

> "Switch it all to MySQL" that the office junior keeps helpfully
> suggesting...

That's not as helpful as he thinks. MySQL is *only* the back end, with no
tools to build the interface. If you get rid of Access, you'll have big
expenses redeveloping front ends to all your databases because they're all
more expensive and take more time than building the front end in Access.

--
Message posted via http://www.accessmonster.com

Access MDB is for ****ing retards

give the mySql reccomender a promotion; show him how to link tables
into Access and put him to work




Granny Spitz via AccessMonster.com wrote:
> John Smith wrote:
> > I have one form, that needs to call DoCmd.Close acForm, "Appeals",
> > acSavePrompt.
>
> As Joan advised, you probably don't need to save the form's design every time
> the form closes. But do all the users have a copy of the front end on their
> desktops? This would be a bigger issue if users were sharing the front end
> on the server.
>
> > When this is called, the application crashes
>
> As Joan advised, make sure the code is compiled *before* you run code.
>
> > On a single machine I have removed all the service
> > packs, and this issue does not occur.
>
> Put the service packs back on, at least through Office 2003 SP1. Access 2003
> without the first service pack is less stable.
>
> > "Switch it all to MySQL" that the office junior keeps helpfully
> > suggesting...
>
> That's not as helpful as he thinks. MySQL is *only* the back end, with no
> tools to build the interface. If you get rid of Access, you'll have big
> expenses redeveloping front ends to all your databases because they're all
> more expensive and take more time than building the front end in Access.
>
> --
> Message posted via http://www.accessmonster.com

Thanks for your constructive input Aaron. but like other posters have said,
its not as simple as that.
;-)

Right, I've time today to play about with it, and get the service packs on
the machine. Each of the clients has a local copy of the front end (so Ive
been assured) which connect to the tables all held on a server.

I'll look into that save command as well, as Ive no idea what its doing. The
form it'sself is static though, so theres no reason why they should be
saving it, maybe the person that threw this all together thought that they
needed to save the information on the form to get it saved into the
database.

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Access MDB is for ****ing retards
>
> give the mySql reccomender a promotion; show him how to link tables
> into Access and put him to work
>
>
>
>
> Granny Spitz via AccessMonster.com wrote:
>> John Smith wrote:
>> > I have one form, that needs to call DoCmd.Close acForm, "Appeals",
>> > acSavePrompt.
>>
>> As Joan advised, you probably don't need to save the form's design every
>> time
>> the form closes. But do all the users have a copy of the front end on
>> their
>> desktops? This would be a bigger issue if users were sharing the front
>> end
>> on the server.
>>
>> > When this is called, the application crashes
>>
>> As Joan advised, make sure the code is compiled *before* you run code.
>>
>> > On a single machine I have removed all the service
>> > packs, and this issue does not occur.
>>
>> Put the service packs back on, at least through Office 2003 SP1. Access
>> 2003
>> without the first service pack is less stable.
>>
>> > "Switch it all to MySQL" that the office junior keeps helpfully
>> > suggesting...
>>
>> That's not as helpful as he thinks. MySQL is *only* the back end, with
>> no
>> tools to build the interface. If you get rid of Access, you'll have big
>> expenses redeveloping front ends to all your databases because they're
>> all
>> more expensive and take more time than building the front end in Access.
>>
>> --
>> Message posted via http://www.accessmonster.com
>

you dont need to install service packs; that is just the half of it

http://officeupdate.microsoft.com



John Smith wrote:
> Thanks for your constructive input Aaron. but like other posters have said,
> its not as simple as that.
> ;-)
>
> Right, I've time today to play about with it, and get the service packs on
> the machine. Each of the clients has a local copy of the front end (so Ive
> been assured) which connect to the tables all held on a server.
>
> I'll look into that save command as well, as Ive no idea what its doing. The
> form it'sself is static though, so theres no reason why they should be
> saving it, maybe the person that threw this all together thought that they
> needed to save the information on the form to get it saved into the
> database.
>
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Access MDB is for ****ing retards
> >
> > give the mySql reccomender a promotion; show him how to link tables
> > into Access and put him to work
> >
> >
> >
> >
> > Granny Spitz via AccessMonster.com wrote:
> >> John Smith wrote:
> >> > I have one form, that needs to call DoCmd.Close acForm, "Appeals",
> >> > acSavePrompt.
> >>
> >> As Joan advised, you probably don't need to save the form's design every
> >> time
> >> the form closes. But do all the users have a copy of the front end on
> >> their
> >> desktops? This would be a bigger issue if users were sharing the front
> >> end
> >> on the server.
> >>
> >> > When this is called, the application crashes
> >>
> >> As Joan advised, make sure the code is compiled *before* you run code.
> >>
> >> > On a single machine I have removed all the service
> >> > packs, and this issue does not occur.
> >>
> >> Put the service packs back on, at least through Office 2003 SP1. Access
> >> 2003
> >> without the first service pack is less stable.
> >>
> >> > "Switch it all to MySQL" that the office junior keeps helpfully
> >> > suggesting...
> >>
> >> That's not as helpful as he thinks. MySQL is *only* the back end, with
> >> no
> >> tools to build the interface. If you get rid of Access, you'll have big
> >> expenses redeveloping front ends to all your databases because they're
> >> all
> >> more expensive and take more time than building the front end in Access.
> >>
> >> --
> >> Message posted via http://www.accessmonster.com
> >