Setting up Accpac on New Machine

[tolver]

HELP!

I have loaded the program files (5.2) on a new XP machine and am trying to link it to the data but I am at a loss. I've done the dump and load, but when I'm loading the dataset it stops at GL01.dat and says its unable to load.

I'm not even sure if dump and load is the appropriate procedure.

Thanks in advance.

Tracey

 

[Jay Converse]

What version of Pervasive is installed?
Are there other errors besides "Unable to load"?

 

[tolver]

Pervasive 2000i that came with the 5.1 discs (sorry, I was mistaken in my original post, I'm at version 5.1).

No other errors on any other machines (2000) and no other apparent issues on the XP.

 

[Jay Converse]

2000i workgroup or server? Did you patch it to SP4?

 

[ettienne]

Check your folder where the dump files are.
I suspect your *.REC files are in a subfolder and not in the root of the folder where they should be. This is a very common mistake when files are unzipped.
For example your dump files should be in \SAMINC\*.REC and not in \SAMINC\SAMINC\*.REC

 

[tolver]

Its the workstation engine and I haven't done anything other than install from the accpac disc - which worked fine on my 2000 machines.

as for the *.rec files, they are in the appropriate folder

 

[tolver]

I'm running the load on the 2000 machine to see if it is the files themselves or if it is an issue with the XP setup/compatability.

 

[tolver]

It isn't working on my 2000 machine either, I'm getting an error message "Unable to update GL01.

 

[Jay Converse]

I think Ettienne is right, you're not pointing to the right Dbdump folder. If the folder is C:\Mydump, then you need:

C:\Mydump\Mycomp.DCT
C:\Mydump\Mycomp\*.REC

 

[tolver]

I changed the directory for the dump and was able to load, but it didn't help with connecting on the new machine, is there a pervasive setup I should be looking at?

 

[Jay Converse]

I'm way confused. You were able to load, but you can't connect?

 

[tolver]

You are not confused. I loaded the data into the defined dataset on my XP machine and when I load ACCPAC it is not available to me.

You'll see in my first post that I wasn't even sure if this was the correct procedure for connecting to the data on the new machine, but either way, I wasn't able to load data. I now know why, but apparently that wasn't my problem.

Guess I'll call a CI ***sigh***

 

[tolver]

Oh, and thank you all for your assistance. If there is anything else you can think of, I will check back, but I think it's time I gave up and hired someone to handle this for me. I've got other things to do with my time, like my job, LOL.

Thanks again.

Tracey

 

[Jay Converse]

You're still not making sense. One of the correct ways of moving Accpac data around is a Dbdump/Dbload.

If you can execute a Dbload, then you can access all the data.

So what exactly do you mean by "it is not available to me"? What is the error message?

 

[tolver]

When I load Accpac, the company set is not there for me to log into.

The data is on our server and the new client machine cannot access the data. It isn't being properly directed to the data (the data is not being moved, I merely need to connect the client to the database).

 

[Jay Converse]

In that case, no Dbdump or Dbload has ever been necessary. All you need to do is ensure that the Accpac SharedData key is pointing to the right folder, i.e., the folder on the network that contains SITE, COMPANY, and USER. Find that folder, and set it in HKEY_LOCAL_MACHINE\SOFTWARE\ACCPAC INTERNATIONAL, INC.\ACCPAC\Configuration\SharedData.

 

[ettienne]

Why did you do a database load then????

Did you point your shared data folder to the share on the server? I assume not.
Check the registry setting for HKLM\SOFTWARE\Accpac International, Inc.\ACCPAC\Configuration\SharedData - compare this to the same registry entry on a computer where Accpac is actually working, they must be the same.

 

[tolver]

Again, if you note my first post (and again later) I stated I wasn't sure if that was what I needed to do to get the client machine linked. I'm technically savvy enough to figure things out, but sometimes you have to try a few things before you do and sometimes, you have to ask for help along the way.

Its working now, so thank you both very much for your assistance, you've been great!

 

[ettienne]

For the benefit of others, what was the problem and how did you fix it?

 

[tolver]

The problem was the registry key, as you both had noted. Once I edited the registry it worked.

Thanks again.