I apologize for being so new to this, but I hope someone may be able to help
me.

We use Businessvision 7 at our office, which works with Pervasive.SQL 2000
Workstation. I'm trying to install Maximizer 9, but it uses Pervasive.SQL v9.
1. When I install Maximizer, Businessvision stops working, and vice versa.

I thought that Pervasive.SQL v9.1 was backwards compatible, so that BV would
continue to work, but that doesn't appear to be the case? Does anyone know
if it's possible to use both programs on the same computer (simultaneously)?
Or am I out of luck?

Thank you for your time.

--
Message posted via DBMonster.com
http://www.dbmonster.com/Uwe/Forums....asive/200604/1

Can you be a lot more specific than "stops working"? All Btrieve
programs get a Status code back from the engine that indicates what is
wrong. Knowing the status code is the key to figuring out how to fix
the problem...
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Austin: Pervasive Service & Support Class - 05/2006 ***
*** Chicago: Pervasive Service & Support Class - 07/2006 ***

lmyers via DBMonster.com wrote:

Sorry for not being more specific.

With Pervasive.SQL 2000 Workstation running in the background, if I try &
open Maximizer 9, it simply will not open one of the address books (databases)
.. When I click on the address book, nothing happens - the screen just
refreshes (and I can keep clicking away, with nothing happening). I also
tried creating a new address book with 2000 running, and when it tries to set
it up, you get the following error:
Title - "DATAMANAGER returned an error code of 30"
Issue - A FILE NAME error occurred on the 'User' file. The file is either
not a Btrieve file or was created by an earlier version of Btrieve.
This is followed by a hundred more error messages, as it tries to create
another workbook, all with the code 30, detailing something about not being a
Btrieve file.
Surprisingly (I just found this out), after entering through all the errors,
it appears to open the program ok, and I even tested adding a contact to the
Address Book, and it seems to work. I closed the program and reopened it,
and you still get quite a few errors when opening, but the contact is still
there. Do you think I can use the program this way, or is that a bad idea?

With Pervasive.SQL v9.1 Workgroup Engine running in the background, I can
open Maximizer 9 without any errors (and I can open the old address books, as
well as the one I just created with 2000 running). When I try to open
Businessvision 7.01A, I make it through the log in screen, at which point I
get the following error:
Title - File Access Error
Issue - An error has occurred while trying to access data
Version - V7.01A 01/12/06
Function - System Startup
File Description - User
File name - C:\BV\Users.btr
Status Code - 000099
Error Message - The NetWare Runtime server is impro...
configured.

When I hit OK (my only option), I get the next error, which is:
Title - BusinessVision.exe - COBOL Text Window
Issue - Execution error: file 'behaviour'
error code: 114, pc=0, call=1, seg=0
114 Attempt to access item beyond bounds of memory (Signal 11)

When I hit OK (again, my only option), it closes the program.

So, that being said, do you think I will run into problems, if I continue to
run Pervasive 2000 and just ignore the start-up errors on Maximizer 9? Or do
you think there is a way to run BV 7.01A on Pervasive v9.1?

Thank you again for your time & your response.

Bill Bach wrote:
--
Message posted via http://www.dbmonster.com

That makes more sense. The Status 30 you get from Maximizer is due to
the fact that some of the files they want to access are probably in the
V9 file format. When you go after it with PSQL2000i, the V7 engine
cannot open the V9 files, and you get the Status 30.

It *MAY* be possible to resolve this, but you'd need the help of
Maximizer. First, find out from them if they support you running on
the PSQL2000i engine, and on the V7 file format. If so, then you can
use the Rebuild Utility built into PSQLv9 to rebuild the Maximizer
files all back down to the older V7 file format. Once you've done
that, you'll be able to open Maximizer without the 30's. If they don't
support this option, then we have another problem...


The other way has potential, too. However, the Status 99 is quite
unusual, and is probably wrong. Here's what you can do:
1) Start PSQLv9.
2) In the PSQLv9 Pervasive Control Center (PCC), enable MKDE Tracing.
3) Run BV to get the error.
4) Disable MKDE Tracing.
5) Scan the trace file for any Status Codes that you might see.
Hopefully, something beyond a 99 will be findable.

While you're in the v9 PCC, change the setting for "Embedded Spaces" in
the Microkernel Router as well. This should be OFF for best backward
compatibility. Of course, if Maximizer decided to require this be on,
that we have yet ANOTHER problem to deal with.


If you're still stuck in the end, I'd suggest investing in some extra
memory and either VirtualPC or VMWare Workstation, then run one of the
applications in a virtual machine instead.
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Austin: Pervasive Service & Support Class - 05/2006 ***
*** Chicago: Pervasive Service & Support Class - 07/2006 ***

lmyers via DBMonster.com wrote: