Re: Migration from native Btrieve calls to SQL with ZEOS components

Bill,

Bill Bach wrote:
This is a very unusual approach. What kind of application is this for?
There are several applications for a process optimization system fo
rubber injection moulding machines. Its calculating state of cure
(vulcanisation).

I just cannot fathom why a new database would be needed every month.
There are two facts why we need new (small) databases:
documentation:
Some Customers want to keep the information on CD-ROM. Ok, saving on CD
and deleting old records is a possibility.
Batch database:
The rubber compound is made by the supplier batch by batch of about 200
kg. More than batch per shift and machine is needed. Each batch is
slightly different, so batch characterisic is taken in account to
optimize quality an cycletime of the machines. So you have a lott of
batch data records wich are partially needed at offline-systems whitout
network access. So they are transported by USB-Stick.

This makes accessing history a LOT more difficult than it should be,
and users may be doing this simple because they do not know any better
way
Most users know nearly nothing about database, Btrieve, Pervasive and so
on. It has to work. And it works very well.

What exact database version are you using? Obviously it is PSQL2000i
or newer, since the PCC was introduced in that version, but it could be
PSQLV8, PSQLv9, or PSQLv10, and the capabilities may vary between
versions.
At our Customers we have nearly every version from 6.15 to 9.5.
It is clear, that 6.15 will not work with SQL.

As for not wanting software on the server, then it is clear that your
customers also do not understand the benefits of client/server
capabilities, and the stability and performance gains that it offers on
any multi-user system.
ACK
And this is also true for us. We are not the IT and database freeks. We
are process application engineers. Databases are "only" tools for us.


If they really want to continue (and I recommend against it), then
you'll have to have some tricks up your sleeve. You can use the modern
Distributed Tuning Objects (DTO) calls to create the database for your
user, using something like this (copied from the manual):

Dim result As dtoResult
Dim database As DtoDatabase
Set database = New DtoDatabase
' Set properties for new database
database.Name = "MYDATABASE"
database.DdfPath = "C:\test"
database.DataPath = "C:\test"
database.Flags = dtoDbFlagCreateDDF + dtoDbFlagRI
result = my_session.Databases.Add(database)
If NOT result = Dto_Success Then
MsgBox "Error"+ Session.Error(result)
End If

Of course, you must also connect to the server and provide a valid
username/password before running this script. If you are ONLY using
Workgroup Engines, though, then you do NOT need a password, as the WGE
does NOT implement database security at all. In short, you can provide
"Administrator" and no password, and a WGE will allow you in.

See the DTO documentation (provided with the product) for more detailed
information. On older systems, you may need an additional DTO
installation, although PSQLv10 systems should be fine...
Thanks a lot!
I will try that.

Axel

.

Relevant Pages

  • Re: Migration from native Btrieve calls to SQL with ZEOS components
    ... It sounds like you just need high-speed database ... The rubber compound is made by the supplier batch by batch of about ... At our Customers we have nearly every version from 6.15 to 9.5. ... See the DTO documentation for more ...
    (comp.databases.btrieve)
  • Performance optimization vs satisficing (was Language Oriented Programming)
    ... >machines that were too small. ... Microsoft has been a leading offender here. ... >arcane issue for server engines. ... magnitude slower, yes, I recall working on a 200mb database, trying to ...
    (comp.object)
  • RE: Store Added Value List Items
    ... You could even union that query with the actual list from the form ... Each user in this database needs to have access to all the same customers. ... is praticle to create a seperate one field table to store values for a lookup ...
    (microsoft.public.access.formscoding)
  • Re: Please suggest relationships model
    ... Providing Customers A Resource For Help With Access, ... However, if he wanted his database quick and painless, I provided ... Here you are in the newsgroup offering services that were NOT ASKED for. ... the newsgroups and a few larger jobs. ...
    (microsoft.public.access.queries)
  • RE: Store Added Value List Items
    ... (The Primary Key that the user updated added) ... Each user in this database needs to have access to all the same customers. ... is praticle to create a seperate one field table to store values for a lookup ...
    (microsoft.public.access.formscoding)