TCP/IP problem?

[Tcs]

I don't know if this is the best group for this question, so if you think a
different group would be better, please advise...

I have a problem which started a little over a week ago. While debugging my
Access .mdb VBA code, the machine would start to get *really* slow, and stop
communicating with our Notes server, and/or our print server. When trying to
reboot, *almost* could not get response to get XP to shut down. The last time
this happened last week I couldn't even get Task Manager to respond.

I posed the question in the Access vba newsgroup, as it seemed logical that *I*
was the cause, with my VBA code. The response I got talked about losing
resources as I got knocked out of my code and restarted. So...since then, I've
been getting out of my .mdb occasionally, and haven't had any problem. Until
this morning, that is.

This morning, the first time my PC started acting up, I hadn't even gone into my
..mdb. And although the second time I had, I wasn't debugging any more. I was
printing several reports. All of a suddent my PC could no longer find the Notes
server, nor could it talk to the print server. (Both are across the street, in
another building, along with our AS400 and other windows servers.) We already
know that our network performance is less than stellar. (Bad implementation
that we're trying to fix, but it's been slow.) We also know that we have a
resource hog of a system printer in accounting, which can, and does, suck up
bandwidth, causing these probelms intermittently for users. But every time I've
had my problem recently, rebooting solves it. *THIS* makes me think that it's
just my PC, and not some 'outside' cause.

So my question basically is, how do I track down my problem? What should I be
looking for? I tried once using Task Manager to see if available memory was
dwindling away, but the numbers didn't look any different than normal. So I'm
at a loss.

Because I was having a problem communicating with the print server across the
steet, I set up our group printer here in the same room as I am, using a local
port. Initially, this didn't work, because at the time, my PC wasn't talking
with anything on the network. As soon as I rebooted, it worked just fine.

When it starts to act up, it seems that it can't communicate via TCP/IP. A
little while ago, it happened again. After printing perhaps a hundred pages of
my print job, the printer just stopped. As soon as I rebooted, away it went.

Any help, suggesstions, ideas would be appreciated. (I have too little hair left
on top to start pulling out.)

Thanks in advance,

Tom




System:

Gateway P4, 2.6GHz, 1.25gb RAM
Windows XP, sp1
Office 2000, sp3

[MarkInSalemOR]

This by no means is a miracle cure, someone else will have to come up with
that.

One if it's doing this when printing to a particular printer do some
research if there are any known memory leaks when using that driver.
Hopefully any information you find on it offers some work-arounds. If you
can't find anything consider reinstalling the printer driver on your system.

Two, go through your code and make sure you are properly closing and
destroying any objects you create. I suggest at the end of every routine you
create using code like the following.

If Not Object is Nothing then
set Object = Nothing
End if

I suggest this format in case the object has already been destroyed you
won't get an error. Afterall you can't set nothing to nothing. If you have
module level objects be sure to put this code in the appropriate unload event
for the module. Or have you're close button do the object destruction.

Three, it appears part of the problem is with your reports. Is it practical
to rewrite one using Excel or Word or put the report in a separate mdb? This
may narrow down the source of the problem.

Four, are you using any Add-ins? Can you test if this problem occurs when
you remove one? In a similar fashion your references in the project.

~Mark



"Tcs" wrote:

> I don't know if this is the best group for this question, so if you think a
> different group would be better, please advise...
>
> I have a problem which started a little over a week ago. While debugging my
> Access .mdb VBA code, the machine would start to get *really* slow, and stop
> communicating with our Notes server, and/or our print server. When trying to
> reboot, *almost* could not get response to get XP to shut down. The last time
> this happened last week I couldn't even get Task Manager to respond.
>
> I posed the question in the Access vba newsgroup, as it seemed logical that *I*
> was the cause, with my VBA code. The response I got talked about losing
> resources as I got knocked out of my code and restarted. So...since then, I've
> been getting out of my .mdb occasionally, and haven't had any problem. Until
> this morning, that is.
>
> This morning, the first time my PC started acting up, I hadn't even gone into my
> ..mdb. And although the second time I had, I wasn't debugging any more. I was
> printing several reports. All of a suddent my PC could no longer find the Notes
> server, nor could it talk to the print server. (Both are across the street, in
> another building, along with our AS400 and other windows servers.) We already
> know that our network performance is less than stellar. (Bad implementation
> that we're trying to fix, but it's been slow.) We also know that we have a
> resource hog of a system printer in accounting, which can, and does, suck up
> bandwidth, causing these probelms intermittently for users. But every time I've
> had my problem recently, rebooting solves it. *THIS* makes me think that it's
> just my PC, and not some 'outside' cause.
>
> So my question basically is, how do I track down my problem? What should I be
> looking for? I tried once using Task Manager to see if available memory was
> dwindling away, but the numbers didn't look any different than normal. So I'm
> at a loss.
>
> Because I was having a problem communicating with the print server across the
> steet, I set up our group printer here in the same room as I am, using a local
> port. Initially, this didn't work, because at the time, my PC wasn't talking
> with anything on the network. As soon as I rebooted, it worked just fine.
>
> When it starts to act up, it seems that it can't communicate via TCP/IP. A
> little while ago, it happened again. After printing perhaps a hundred pages of
> my print job, the printer just stopped. As soon as I rebooted, away it went.
>
> Any help, suggesstions, ideas would be appreciated. (I have too little hair left
> on top to start pulling out.)
>
> Thanks in advance,
>
> Tom
>
>
>
>
> System:
>
> Gateway P4, 2.6GHz, 1.25gb RAM
> Windows XP, sp1
> Office 2000, sp3
>
>