error message

[randva]

Macola 7.5.102e, Pervasive SQL

I have one user who sometimes gets this error when attempting to open Macola. Can anyone tell me what it means or how to fix it?

Execution error file
'MAC32UP.LBR\Screenw.gnt'
error code: 166, pc=0, call=6, seg=0

Any help is greatly appreciated.

 

[abaldwin]

More info please. What is the network configuration (i.e. NT Novell, etc).

What DB version of Pervasive?

What is the workstation OS having the problem?
Also is this happening for this user on one workstation or any that they log into?

Is this before or after putting in the macola password?


Out of curiosity....Why such an old version of the softare?

Thanks

Andy Baldwin

"Testing is the most overlooked programming language on the books!

 

[abaldwin]

BTW the closest thing I can find to that error (and I have never personally seen a 166) is to reinstall the client on the machine. Personally I would uninstall both the pervasive client as well as the macola client and re-install both.

Andy

Andy Baldwin

"Testing is the most overlooked programming language on the books!

 

[randva]

Mr. Baldwin:

Thank you for your suggestion.

Pervasive SQL 7.0, NT 4.0 server with about 20 XP clients. I have not tested that user name on other workstations. The error occurs before the login window appears (so before a password has been put in)

A corporate decision was made to fix our version at 7.5.102e. It generally works for our needs. We have purchased custom interfaces to upload and download EDI orders / invoices. We also purchased PEAK enhancements (then they were a 3rd party add on).

The cost and time of upgrading and making everything work was deemed not worth the incremental improvements (not to mention new bugs) that Macola offered in new releases. Eventually we will just buy a new license. But not yet.

Again, thank you for your help with this error.

 

[abaldwin]

Let me know if re-installing the client works for you.

Also insure the user has proper rights on the machine and is signing into the domain properly.

You can test this by signing in as you, or another user who has admin rights and see that it works.

BTW What do you mean "(not to mention new bugs)" There are no bugs in Macola. (can you hear my sarcasm here????) Just undocumented challenges for IT professionals to get stars on tek-tips with.

Have a good day.


Also, I appreciate the respect of the MR. you put in your response, but seriously, Just call me Andy.



Andy Baldwin

"Testing is the most overlooked programming language on the books!

 

[MacolaHelp]

Your user screens may also be corrupt. Can you delete this user and their modified screens & reenter the user fresh & copy their screen sets from a user that doesn't have problems? Also, check that your users have full permissions in the registry to hkey local software macola, odbc, and pervasive on the local xp machine. The user should also be a local administrator of the workstation.

I'm with Andy, get off 102e. It was not the best 102 release. 102f & 100a are far better. I thought 7.6.200 & 200.5 were terrible (the first stab at switching to dll technology). 300c seems okay for those not using Peak Best OE previously. There are still some issues with integrating the Peak into vanilla Macola. A 166 error is pretty wierd.

If all else fails, there are some old btrieve gurus out there that might know the root cause of a 166 and I can send you in their direction. Post back and let me know.