> Me? Not adventurous at all, at least as far as code
> is concerned, when dealing with fixed-price projects.
> I find it easier to just write something to do this,
> then if I get a newer Delphi, maybe I'll use the
> importer as it's guts, but even then it *really*
> depends.....

Not sure I understand. Suring having the TIB_Import code already
written it should be a simpler to work out which bits dont work in
Delphi3 and implement a work around, than it would be to start from
scratch.

> Hmmm, I'll take a look, didn't see anything before...

A lot depends on what you need. I have various transfer code in my
own collection, but none of it will help you in D3 (some is in C, some
in D5).

I do admit that TIB_Import/TIB_Export leave some things to be desired.
I have started to write something that saves import/export rules to a
file, so that the same transfer can be run over and over again. I use
this sort of thing a lot when preparing to upgrade or crossgrade
databases. So far most of it is has only gotten to the stage of being
useful for me, without ever getting solid enough to share. All I need
is a few spare months :-)


Geoff Worboys
Telesis Computing