Re: no server engine, only local workstation engines, Status 116
- From: Leonard <lharvey@xxxxxxxxxxxxx>
- Date: Sun, 19 Feb 2006 04:27:23 GMT
In a workgroup environment if the engines are only accessing their own
data you can mix and match versions as you like.
Perhaps I wasn't clear enough though.
If you are getting a 116 the multiple users are sharing a single
database instead of only woking on their own local database.
From what you say this is not what you want. You may want to check onjust how the users are running the application to get the status 116.
In answer to your question, "can you turn off the Workgroup features
and run in "Workstation" mode?" Yes. Just turn off the "use remote
Microkernel" in the client settings and turn off the "Allow Remote
Requests" in the engine settings. And yes if they try to access data
another user (engine) has open they will then get a status 116.
Leonard
On Fri, 17 Feb 2006 17:26:19 +0100, Axel Potthoff <apn51@xxxxxx>
wrote:
Hi,
Leonard wrote:
Gil is correct. If any of the applications access the same data set
or database they should all be the same version.
All the databases are version 7 due to history.
But one question: Do you go to your customer an tell him to upgrade 9
workstations to version 9 because of one new system? Are they willing to
pay for it? For the licenses, for the installation, the configuration and
(if you act consequently) converting the databases to the latest version?
We are out of the job, when we offer somenthing like that to our customers.
I accept, that Pervasive turns the back to version 5 databases when stepping
to version 9. But I don't accept updates to every workstation every year.
An one other question:
Isn't it possible to adjust an local Pervasive engine as a LOCAL WORKSTATION
ENGINE?
* no workgroup functions
* no gateway functions
* no remote requests
* no acception of remote requests
* working only local
This worked well with Version 6 (or was it 7?), when workSTATION engines
were availiable!
Because of changing our applications from native btrieve calls to SQL, we
think of changing to other database engines.
Axel
.
- References:
- no server engine, only local workstation engines, Status 116
- From: Axel Potthoff
- Re: no server engine, only local workstation engines, Status 116
- From: nelsonsoft
- Re: no server engine, only local workstation engines, Status 116
- From: Leonard
- Re: no server engine, only local workstation engines, Status 116
- From: Axel Potthoff
- no server engine, only local workstation engines, Status 116
- Prev by Date: Re: Strang behavior of Backup-Agent 1.0
- Next by Date: Re: Server configuration PSQL 8.x after installation
- Previous by thread: Re: no server engine, only local workstation engines, Status 116
- Next by thread: Page server invalidation list is full
- Index(es):
Relevant Pages
|
|