Bill,
I have to explain my basic problem a little more:
We have no DOS applications any more. We do Btrieve calls in Windows.
We don't use DDF files until now.
We use local workstation engines. Our customers don't like someone,
installing something on their server.
But we want to change to SQL do be more flexible to changes in the
structure.
Bill Bach wrote:
> ...
> As for your "new" ADO application -- why are the users creating
> databases? The users should be accessing databases created by the
> developers and/or database administrator, and they should not be
> creating new ones.
We started with Btrieve 5.15.
The users do this since 15 years or more.
They say, "The month is over, let us start with an new data file for
do***entation."
They take the data file, put it to a USB stick an read data records at
an offline system.
With native Btrieve this all was no problem. "One file = one table". A
simple call of function 14 and you have an new data file. The structure
is made by our application, but filename and location can be choosen
freely by the user. We have not had any problems in the past.
And that is all what we want.
But now, the controlcenter has to be used. You are right, that is
nothing for the user! And the controlcenter writes something to the
C:\WINDOWS\DBNAMES.CFG and maybe elsewhere before I can connect the
datafiles.
Is there no simpler solution?
Axel
|
