Skip to main content

Replies sorted oldest to newest

Hi,

You really need to not use "Standby", "Hibernate" etc with a current Max session active.

What happens is that the server cannot see your computer, so it assumes it went down dirty, i.e. crashed, and it closes the database connection.

When your machine wakes up, it expects to see everything just the way it was. It tries to use the database connection it had before, but now it doesn't work.

There's no workaround for this, and its not a bug. The thing to do is to close your Max session before your machine goes to sleep.

- Pasta
Sorry, O just re-read your post and saw the problem ws with window minimize/maximize, not going to sleep. Ignore my previous post! Roll Eyes

The size of the window *should" have no effect at all. I would suggest an uninstall, power-off, re-install, and then adding all relevant service packs. I can only imagine some corruption somewhere casuing this problem.

- Pasta
Pasta:

>Ignore my previous post!

For future reference, this board allows you to edit or delete your posts for 60 minutes after you submit them. Great for correcting typos, etc..

>The size of the window *should" have no effect at all.

Precisely, which is why when ozzy75 mentioned PCMCIA I thought "notebook", and when I thought "notebook" I thought "power management".

ozzy75:

Are you saying that when you are working away in Maximizer, if you minimize the Maximizer window and then immediately restore it you get a code 3006? Every time?
I've seen this error message a few times in dealing with Max and it means that the network connection between the workstation and the server was lost. As Gord mentions, enable the Pervasive auto-reconnect. - that has fixed it in my experience. If that doesn't work, you may be looking at underlying network problems that are "manifesting" in Max.

Add Reply

Post
LEGAL INFO
CONTACT US
Copyright 2007-2018 Advoco Solutions Ltd. All Rights Reserved.
×
×
×
×
Link copied to your clipboard.
×