At 02:34 PM 11/30/2000 -0300, you wrote:

>Take a look at
>
>http://www.ibphoenix.com/sql2gdb.html

Last version I used still was iffy.

You need to make accomodations for a lot of things. For one IB can not
handle long object names or object names with spaces or other "unusual"
characters in it. Also you need to build your tables with a case insenstive
collation if you don't want to break your access app.

<vent>

How I wish some database manufacturer (other then MS) would create a
simple, robust database that
a) supported case insensitive, long (255 character) object names which
allowed spaces and such
b) Had a very good cursor based ODBC/ADO driver.
c) Had a good optimer for the crazy SQL access spits out
4) Had declaritve refential integrity including cascaded updates and deletes
5) was platform independent
6) supported a decent trigger language or emitted events so that you can
code your triggers in any language you choose.
7) supported database wide collation options instead of specifying them per
table, column, or session including case insensitive collation options.


I Really don't care that much about built in functions or Stored procedures
IMHO those things could be done very efficiently in some middle tier. A
database server ought to keep the data safe, the tables related and be able
to efficiently execute queries. There are a lot of things I hate about
access but there are a lot of things I like too. If there was a clone of
access with a more robust locking mechanism, and better concurrency it
would take over the world.

</vent>


:wq
Tim Uckun
Due Diligence Inc. http://www.diligence.com/ Americas Background
Investigation Expert.
If your company isn't doing background checks, maybe you haven't considered
the risks of a bad hire.