Hello,
I have an Access 2000 file working on XP machines and a NT network.
The files are split and 95% of the time all is well and stable. The
main issue arises when the app prints,a novell netware pop up shows
and declares which printer the file is going to and when printing
completes, Access crashes. This is really starting to tick off the
client users.
I see that there may be two possible solutions - first, I have some
way of shielding the access file from the action or secondly get the
IT staff to switch off the popup.
Anyone had a similar problem and perhaps even suggest another possible
cause or a possible fix.
Many thanks
John

The popup itself is really not the problem - the problem is you have an
unhandled error that is causing Access to crash. More than likely some sort
of printer error is being generated. Do you have an error handler around
the print routine? What happens when you do print preview, then print -
does it generate the same error, and at what point?

Darryl Kerkeslager



"Jamma" <fly_mo@hotmail.com> wrote:[color=blue]
> Hello,
> I have an Access 2000 file working on XP machines and a NT network.
> The files are split and 95% of the time all is well and stable. The
> main issue arises when the app prints,a novell netware pop up shows
> and declares which printer the file is going to and when printing
> completes, Access crashes. This is really starting to tick off the
> client users.
> I see that there may be two possible solutions - first, I have some
> way of shielding the access file from the action or secondly get the
> IT staff to switch off the popup.
> Anyone had a similar problem and perhaps even suggest another possible
> cause or a possible fix.
> Many thanks
> John[/color]

Hi Darryl,
Thanks for the response.
There is error trapping on the reports and the client has stated that
they have the same problem with msWord occasionally. The error occurs
after all selected reports are printed, the access window passing the
reports to the printer has closed, the popup appears then the "Access
has develpoped a serious error and must be closed" warning appears.

I have used this app at another client and on two different test
machines without the error - it seemed logical that this was the only
immediate difference that I could see.
I haven't noticed that it happens after previewing first - what might
that indicate.

John

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

> I haven't noticed that it happens after previewing first - what might[color=blue]
> that indicate.[/color]

Based on what you've said, probably nothing, but soetimes it can point out
if the error is in the report formatting code or in the printing.
[color=blue]
> There is error trapping on the reports[/color]

I was more interested in whether the actual DoCmd.OpenReport was trapped.
[color=blue]
> I have used this app at another client and on two different test
> machines without the error - it seemed logical that this was the only
> immediate difference that I could see.[/color]

Are the Windows and Access versions the same? Could low memory be an issue?
Based on what you've said, probably not. There was a change in the
OpenReport between 97 and 2000 that caused some run-time errors in a certain
case (I can't remember the details).

Have you tried printing from the same exact machine on different printers?

Have you tried peppering your code with MsgBox statements to pinpoint
exactly the line of code where the error occurs? If the error was in fact
caused by the Netware popup, which would not presumably happen at the exact
same time every time, then the error could/should happen in different places
in your code, depending on execution speeds.

Darryl Kerkeslager




"John McCusker" <fly_mo@hotmail.com> wrote:[color=blue]
>
> Hi Darryl,
> Thanks for the response.
> There is error trapping on the reports and the client has stated that
> they have the same problem with msWord occasionally. The error occurs
> after all selected reports are printed, the access window passing the
> reports to the printer has closed, the popup appears then the "Access
> has develpoped a serious error and must be closed" warning appears.
>
> I have used this app at another client and on two different test
> machines without the error - it seemed logical that this was the only
> immediate difference that I could see.
>
> John
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it![/color]

Jamma wrote:
[color=blue]
> Hello,
> I have an Access 2000 file working on XP machines and a NT network.
> The files are split and 95% of the time all is well and stable. The
> main issue arises when the app prints,a novell netware pop up shows
> and declares which printer the file is going to and when printing
> completes, Access crashes. This is really starting to tick off the
> client users.
> I see that there may be two possible solutions - first, I have some
> way of shielding the access file from the action or secondly get the
> IT staff to switch off the popup.
> Anyone had a similar problem and perhaps even suggest another possible
> cause or a possible fix.
> Many thanks
> John[/color]

Novell still around? <g>

AFAIK Netware uses the Windows Messenger service so try opening a
command prompt (Start->Run->cmd.exe) and type:

net send %COMPUTERNAME% test message

See if Access crashes then.

Try setting up a local printer and printing to that, does it crash then?

Also, be a bit more clear about the word "crash", does it just exit?
Does it give a message then exit? Does it just give messages? Does it
say it has caused a problem and needs to close and offers a "send report
to MS" option?


--
Pretentious? Moi?

The crash does say that there has been an error and needs to send a
report to MS - it then tries to create a backup copy.
The dept that has the application has been trying for a local printer,
but at this point rely on network devices.
I'll have to try the docmd error reporting as suggested by Darryl next.
Many thanks for the responses.
John

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Sounds like the Novell "Notify" message box is popping up, which is
irritating to no end anyway.

Try this:

Right click on the big red 'N' in the system tray and go to client
properties.
Take a look at the default capture tab. There should be a box lablelled
"Notify". If this is checked, turn it off and see if that corrects the
problem. At the very least it should stop the annoying pop-up everytime you
launch a print job. Of course, maybe your clients want to see that.

BTW, we use Novell 6 in our office, and the client installed on all of our
PCs is version 4.90. I mention this because HOPEFULLY your Client
properties has more or less the same tabs. If you have an older version,
you probably need to talk to your sys admin to find out how to get notify
turned off.

Just an aside to Trevor's comment about "Novell still around?<g>" -- Yep, it
is. And going strong. I've worked with some NT boxes, and as far as
downtime or problems, Novell beats the socks off NT. We've been running our
Novell box for 3 years without downtime with one exception -- when we moved
our office from one location to another across town. The Novell box was
installed on the weekend of the move, we came in Monday morning, logged in
and have been happily running ever since with no problems. Can't beat that
with a stick. <G>

Anyway John, Hope This Helps.

Ruben


"Jamma" <nospamfly_mo@hotmail.com> wrote in message
news:416d2d8d$0$24899$c397aba@news.newsgroups.ws.. .[color=blue]
>
> The crash does say that there has been an error and needs to send a
> report to MS - it then tries to create a backup copy.
> The dept that has the application has been trying for a local printer,
> but at this point rely on network devices.
> I'll have to try the docmd error reporting as suggested by Darryl next.
> Many thanks for the responses.
> John
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it![/color]

Many thanks to all for the excellent suggestions & responses - I'm off
to the clients tomorrow in an effort to try these suggestions. One
way or another the crashes have to stop.
Regards
John






"R Baumann" <rynt@9yahoo.com> wrote in message news:<m6WdnebugO2Xq_DcRVn-vQ@megapath.net>...[color=blue]
> Sounds like the Novell "Notify" message box is popping up, which is
> irritating to no end anyway.
>
> Try this:
>
> Right click on the big red 'N' in the system tray and go to client
> properties.
> Take a look at the default capture tab. There should be a box lablelled
> "Notify". If this is checked, turn it off and see if that corrects the
> problem. At the very least it should stop the annoying pop-up everytime you
> launch a print job. Of course, maybe your clients want to see that.
>
> BTW, we use Novell 6 in our office, and the client installed on all of our
> PCs is version 4.90. I mention this because HOPEFULLY your Client
> properties has more or less the same tabs. If you have an older version,
> you probably need to talk to your sys admin to find out how to get notify
> turned off.
>
> Just an aside to Trevor's comment about "Novell still around?<g>" -- Yep, it
> is. And going strong. I've worked with some NT boxes, and as far as
> downtime or problems, Novell beats the socks off NT. We've been running our
> Novell box for 3 years without downtime with one exception -- when we moved
> our office from one location to another across town. The Novell box was
> installed on the weekend of the move, we came in Monday morning, logged in
> and have been happily running ever since with no problems. Can't beat that
> with a stick. <G>
>
> Anyway John, Hope This Helps.
>
> Ruben
>
>
> "Jamma" <nospamfly_mo@hotmail.com> wrote in message
> news:416d2d8d$0$24899$c397aba@news.newsgroups.ws.. .[color=green]
> >
> > The crash does say that there has been an error and needs to send a
> > report to MS - it then tries to create a backup copy.
> > The dept that has the application has been trying for a local printer,
> > but at this point rely on network devices.
> > I'll have to try the docmd error reporting as suggested by Darryl next.
> > Many thanks for the responses.
> > John
> >
> > *** Sent via Developersdex http://www.developersdex.com ***
> > Don't just participate in USENET...get rewarded for it![/color][/color]