Tim Young [Elevate Software] wrote:
> Actually, you could do all of what Rita mentioned in code without user
> interaction.

Tim, do you mean i'll be able to deploy a single exe to upgrade customers'
tables from v3 to EDB in one pass and without user intervention?

Sandra

Jan


Also don't forget the cludge solutions - small program to write sql insert statements which you then run, or export and import the data

Roy Lambert

Sandra,

<< Tim, do you mean i'll be able to deploy a single exe to upgrade
customers' tables from v3 to EDB in one pass and without user intervention?
>>

Yes, although it will involve linking both DBISAM 3.x and EDB into the same
EXE.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Will multiple applications be able to access the same DB if it's a local
client file, or will it be exclusive to an internal server on the client?
(Question is for local tables, not C/S version).

Nonsense ! u wrote the app 1st right so you know the
table structure's in the DB.
Write an app to send V2 or V3 to a delimited file or
use Tim's code to upgrade from one version to the other.
If u cant trust your customers to run an app against the
data then charge them for a service call.
We will all no doubt need to upgrade to EDB soon but
do your customers who are running via V2-V3-V4
need to?
Like I said whats the problem ?

Rita

"Sandra" <sandra70it@gmail.com> wrote in message
news:DCF0E4E9-AE25-4F4C-82E6-FFF125C1CF88@news.elevatesoft.com...
> R. Tipton wrote:
>> use v4 Dbsys to ugrade 3 to 4 then EDBsys to upgrade from v4
>> whats the problem ?
>
> in the fact you couldn't deploy an automatic upgrade procedure to the
> customers!!!
> You should force each of them to send you their archives (imagine the
> privacy problems involved in some cases), upgrade them manually, then send
> new tables back to them, or, alternatively, force them to manual upgrade
> tables (and customers are usually able to make the worst damages even in
> the simplest cases).
>
> Sandra
>

R. Tipton wrote:
> Write an app to send V2 or V3 to a delimited file or
> use Tim's code to upgrade from one version to the other.
> If u cant trust your customers to run an app against the
> data then charge them for a service call.

the problem is that we can't deploy complex upgrade procedures, since
cutomers CAN (and WILL) do mistakes. So the idea to make the customer use
DBSYS, sql statements, and so on, is simply unacceptable. Things must be the
simplest, possibly one-exe and one-click, especially when you've hundreds of
customers to upgrade.

> We will all no doubt need to upgrade to EDB soon but
> do your customers who are running via V2-V3-V4
> need to?

we aren't going to maintain old and new db versions of our apps, so: yes,
they need, unless they want to keep a technologically old and unsupported
version of the software.

Sandra

Sandra wrote:

> R. Tipton wrote:
> > Write an app to send V2 or V3 to a delimited file or
> > use Tim's code to upgrade from one version to the other.
> > If u cant trust your customers to run an app against the
> > data then charge them for a service call.
>
> the problem is that we can't deploy complex upgrade procedures, since
> cutomers CAN (and WILL) do mistakes. So the idea to make the customer
> use DBSYS, sql statements, and so on, is simply unacceptable. Things
> must be the simplest, possibly one-exe and one-click, especially when
> you've hundreds of customers to upgrade.
>
> > We will all no doubt need to upgrade to EDB soon but
> > do your customers who are running via V2-V3-V4
> > need to?
>
> we aren't going to maintain old and new db versions of our apps, so:
> yes, they need, unless they want to keep a technologically old and
> unsupported version of the software.
>
> Sandra


You could code two dll's.

The first dll, we'll call it "v3tov4.dll" would have a simple routine
that would use the TDBISAMTable.UpgradeTable metthod to upgrade from v3
to v4.

The second dll "v4ToEDB.dll", would use the TEDBTable.UpgradeTable*
method to perform the upgrade from v4 to EDB.


Your installer or update program would perform a backup of the existing
data and then call the functions exported from each of these dll's with
a path to the data to upgrade.


* Please note this syntax is a guess, you'll have to verify the actual
calls when ElevateDB ships.

-AJ Marknette

--

Jerry,

<< Will multiple applications be able to access the same DB if it's a local
client file, or will it be exclusive to an internal server on the client?
(Question is for local tables, not C/S version). >>

Multi-user operation will be exactly the same as with DBISAM.

--
Tim Young
Elevate Software
www.elevatesoft.com

> Multi-user operation will be exactly the same as with DBISAM.

Perfect.