I currently have an application that uses dBase (.dbf) format tables with
..mdx index files.

I assume Elevatedb comes with some sort of utilty to convert/import files of
this format? Can someone please confirm this?

Also, does Elevatedb have any support for expression indices i.e.
PERIOD+ACCOUNT? I realize that using such indices for new applications is
not suggested, but I'm hoping to be able to convert my tables into a working
app as is, and then re-structure and re-write as I go along in coverting to
C/S. In order to do this, support of expression indices would be key.

Frank


>I assume Elevatedb comes with some sort of utilty to convert/import files of
>this format? Can someone please confirm this?

As of 1.03b1 there is a bde migration module so I presume its in that. I haven't checked it out since I stopped using the bde yonks ago

>Also, does Elevatedb have any support for expression indices i.e.
>PERIOD+ACCOUNT? I realize that using such indices for new applications is
>not suggested, but I'm hoping to be able to convert my tables into a working
>app as is, and then re-structure and re-write as I go along in coverting to
>C/S. In order to do this, support of expression indices would be key.

I think so via COMPUTED fields.

Roy Lambert

Thanks, but my understanding of computed fields is that they are fields in a
table and have nothing to do with indices.

Frank,

<< I currently have an application that uses dBase (.dbf) format tables with
..mdx index files.

I assume Elevatedb comes with some sort of utilty to convert/import files
of this format? Can someone please confirm this? >>

Yes, we provide a BDE Migrator with EDB that will move over the dBase
tables.  I assume that you have the BDE installed ?

<< Also, does Elevatedb have any support for expression indices i.e.
PERIOD+ACCOUNT? I realize that using such indices for new applications is
not suggested, but I'm hoping to be able to convert my tables into a working
app as is, and then re-structure and re-write as I go along in coverting to
C/S. In order to do this, support of expression indices would be key. >>

EDB supports two kinds of expression columns - COMPUTED and GENERATED, and
both can be indexed.  So, instead of putting the expression in the index,
what you do is you put the expression in the column and then index it.  It
makes the job of the query/filter optimizer much easier and allows one to
see exactly what is being indexed.

The difference between COMPUTED and GENERATED is discussed here:

http://www.elevatesoft.com/scripts/newsgrp.dll?action=openmsg&group=16&msg=912&page=1#msg912

You can define the columns using an ALTER TABLE statement:

http://www.elevatesoft.com/edb1sql_alter_table.htm

Just remember that in EDB you need to drop the column and then re-add it in
the same ALTER TABLE statement in order to change its type or the GENERATE
or COMPUTED clauses.  You can use the ADD COLUMN ... AT clause to specify
exactly where to add it back so that you can put it in the same position as
before.

--
Tim Young
Elevate Software
www.elevatesoft.com

> Yes, we provide a BDE Migrator with EDB that will move over the dBase
> tables.  I assume that you have the BDE installed ?

> EDB supports two kinds of expression columns - COMPUTED and GENERATED, and
> both can be indexed.  So, instead of putting the expression in the index,
> what you do is you put the expression in the column and then index it.

Yes, I have BDE installed. Thank you for your answer.