Re: no server engine, only local workstation engines, Status 116

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


.

Relevant Pages

  • Re: Front End Back End Problems
    ... which is basicly all of our current databases. ... ends are all located on local workstation drives and the ... out the server and there is no reported problems with it. ... >> default workgroup that comes with Access. ...
    (microsoft.public.access.security)
  • Can not make MDE file from a converted Access 2003 database
    ... XP workstation which has Access 2003 since all of our ... converted the databases from Access 2000 format to Access ... could make mde files on the developing workstation without ... I also tried to copy the databases to a Windows 2003 ...
    (microsoft.public.access.conversion)
  • Access 2003 can not make mde file of a Access 2000 database
    ... XP workstation which has Access 2003 since all of our ... converted the databases from Access 2000 format to Access ... could make mde files on the developing workstation without ... I also tried to copy the databases to a Windows 2003 ...
    (microsoft.public.access.setupconfig)
  • Re: exe wont run
    ... rework the program to handle the databases at the server but run from ... The aggregation of the data into local systems has me confused. ... workstations and more than one workstation is accessing the data how ... For multi-user apps, look at locking. ...
    (microsoft.public.fox.programmer.exchange)
  • info and questions on conversion to A03
    ... client databases to Jet4 and then using Access to convert to Access ... Of course, once converted, Access97 can no longer read the database. ... "Engine"? ... It bombs the first time it tries to open the ...
    (microsoft.public.vb.database.ado)