AdressBook's problem in a Max 7.5 pervasive workgroup

>When a user add some new adress book entries on his workstation, I
>cannot see these modifications on mine.

Are you sure you're both looking at the same Address Book? If you are each looking at Address Books in your respective Local Lists, then you're looking at separate databases even though they may have the same name. The shared Address Books are the ones in the Global List.

>Other question: can we logged on Maximizer while the database on
>the server is not running?

You don't need to have Maximizer open on the server, but the Workgroup Engine must be running on that machine. Check the server and make sure that the Workgroup Engine icon appears in the system tray:



(Note that if you have the engine loading from the Startup group on the server then somebody must always be logged on at the server. Many people configure their WGE servers to logon automatically after a reboot - the instructions for that are in Microsoft's Knowledge Base.)

The answer to your first question may be as simple as going to the View menu and selecting "All Companies And Individuals".

Maximizer does not maintain a "dynamic" link to the database. It executes a command, retrieves the relevant information, disconnects from the database, and displays the results. If you have 100 entries in your address book and your workstation adds 3 more records, you'll have a total of 103.

On the server computer, you'll continue to see the 100 records until you re-access the database. Nine times out of ten, that turns out to be the problem.

Thanks; Is there a way to refresh automaticlly the adress book without any manual intervenance?

Nope.

You can, however, set Maximizer to automatically display all companies and individuals when opening the Address Book.

Go to the File menu and click Preferences. On the "System Defaults" tab, put a check in the box for "Ask at program startup which address book list to view." Click OK. Close out of Max. Open it back up again. When you re-open it (or when you re-open an Address Book) you'll be prompted to choose and Address Book list. Select the option for "View all Companies and Individuals", put a check in the box for "Make this my default" and click the OK button.

Now, every time you open your address book in Max, it will display all the companies and individuals.

As for anything in the program that will automatically refresh your screen while the program is open, you're outta luck. Try hitting
F5 to refresh the screen.

I don't think that the refresh function has a real influence for updating the database.

is it the same in a client/server configuration?

quote:

---

Originally posted by Gord Thompson:

(Note that if you have the engine loading from the Startup group on the server then somebody must _always_ be logged on at the server. Many people configure their WGE servers to logon automatically after a reboot - the instructions for that are in Microsoft's Knowledge Base.)

---

I'd be interested in the KB article #.

Certainly one requires an add'l license to install the Pervasive Workgroup Engine but I don't think a user has to be actually logged in.

On our Windows Server 2003 I've configured the WGE to pre-load but there is no users logged on at the server. And, there is no apparent problems for users accessing the database from their workstations!

IRIS

>I'd be interested in the KB article #.

- Go to the Microsoft Knowledge Base search page.

- Select the OS you are using.

- Search for 'automatic and logon'.

- Locate the appropriate article. (e.g. for Win2K it is 310584)

>Certainly one requires an add'l license to install the
>Pervasive Workgroup Engine

Not true. Pervasive Workgroup licenses control the number of clients that can connect to a workgroup server. Installing the WGE on the server does not consume a license.

>On our Windows Server 2003 I've configured the WGE to pre-
>load but there is no users logged on at the server.

Bottom line: If the WGE is not running then it cannot accept connections. It sounds like one of your workstations is assuming the role of the Gateway machine. You can test this by doing the following:

- Verify that nobody is logged-on at the server.

- Launch Maximizer on your workstation and open the shared address book on the server.

- Still at your workstation, open a command prompt and enter the following command...

type \\servername\MxData\whatever\~pvsw~.loc

...substituting your own server's name for 'servername' and the path to your address book for 'whatever'. The contents of that file indicates the machine currently acting as the gateway.

Alternatively, you can use the Pervasive Monitor:

Start > Programs > Pervasive > Pervasive.SQL 2000i > Utilities > Monitor

Launch it on your workstation, then choose

Options > Connect...

Enter the server name and logon credentials, then click OK. Once you've connected to the server, choose

MicroKernel > Active Users...

to see what users are currently connected to that WGE.

(Hint: If you get an error message like this



then the WGE is not running on the server and it cannot be acting as the gateway.)

quote:

---

Originally posted by Gord Thompson:
>Certainly one requires an add'l license to install the
>Pervasive Workgroup Engine

Not true. Pervasive Workgroup licenses control the number of clients that can connect to a workgroup server. Installing the WGE on the server does not consume a license.

---

I was thinking more from an ethical standpoint.

quote:

---

Bottom line: If the WGE is not running then it cannot accept connections. It sounds like one of your workstations is assuming the role of the Gateway machine. You can test this by doing the following:

---

The engine is running - preloaded through startup. Just no users logged on.

quote:

---

- Still at your workstation, open a command prompt and enter the following command...

type \\servername\MxData\whatever\~pvsw~.loc

---

Results:

C:\Documents and Settings\Administrator.TAM>type \\server\MaxData\~pvsw~.loc
Server
\\SERVER\D$\DBase\MaxData\Corporate\~PVSW~.LOC

So, as my original post I don't see why one would have to log on at the server as clearly I'm not and it's working.

Thanks for the syntax to check!

IRIS

P.S. And the KB article - I'll check it out.

Shud the WGE be preloaded only on the server?

Pre-loading WGE at the workstations too didn't always seems to have it connect - that is the indicator turning green - it loaded red more often than green. To reload required stopping it through task manager.

Quit pre-loading at workstation and had it load when Maximizer was invoked. Seems to always be green when done this way - even though Maximizer's article recommends pre-loading so Maximizer itself loads faster.

Just following Maximizer's directions - however, even though they seem clear at first they don't specifically address some questions like this.

Any feedback appreciated!

IRIS

[This message was edited by Iris on December 01, 2003 at 06:29 AM.]

quote:

---

Originally posted by Gord Thompson:
>I'd be interested in the KB article #.

- Go to the Microsoft Knowledge Base http://support.microsoft.com/default.aspx?scid=FH;EN-US;KBHOWTO&sd=GN&ln=EN-US.

- Select the OS you are using.

- Search for 'automatic and logon'.

- Locate the appropriate article. (e.g. for Win2K it is http://support.microsoft.com/default.aspx?scid=kb;en-us;310584&Product=win2000)

---

Gord, I read the article you referred to and perhaps that's where some of the misunderstanding is coming from.

I interpreted logging as you referenced it as to Maximizer but the article refers to Windows OS.

We certainly do need to log on to our Windows Server 2003 after which the WGE pre-loads. However, no Maximizer user is logged on at the server.

The WGE indicator is green at the server.

Refer to my previous post with respect to the workstations.

I do value your feedback - it's been quite heckit as we're rolling out a new server and xp boxes with Max 7.0 (upgrade from 5.0) so I've been busy with many aspects - not just Maximizer. But that doesn't lessen my desire to get Max configured exactly right so users don't run into any probs.

So far I've kept matters to the test lab but we roll out this week as I think (fingers crossed) I've got most of the issues in hand. So like I said if you have any add'l comments I'm sure interested.

IRIS

>Shud the WGE be preloaded only on the server?

It is best if the WGE is pre-loaded on the workstations as well.

>Pre-loading WGE at the workstations too didn't always seems
>to have it connect - that is the indicator turning green -
>it loaded red more often than green.

I've seen that happen, too. I wouldn't worry too much about red/green on the workstations as long as they are able to open the Address Book on the server.

>Maximizer's article recommends pre-loading so Maximizer
>itself loads faster.

Pre-loading on the workstations also helps avoid strange errors that can sometimes appear when launching Maximizer. If the WGE on the workstation is not pre-loaded then it starts up when Maximizer is launched. If Maximizer gets impatient and starts trying to use the engine before it is fully loaded, such errors can occur.

>We certainly do need to log on to our Windows Server 2003
>after which the WGE pre-loads. However, no Maximizer user
>is logged on at the server.

Yes, that's what I meant.

BTW, as an alternative to pre-loading the WGE in the Startup group I've also had good success with running it as a service via the SRVANY utility.

quote:

---

Originally posted by Gord Thompson:
>I wouldn't worry too much about red/green on the workstations as long as they are able to open the Address Book on the server.

---

Yes, the Address Book has been able to load despite the red/green indicator status on the wkstn. FWIW, I'll configure the wkstns to preload the WGE.

Thanks for your feedback!

IRIS