Warning, this is a translating service...
;-)

> -----Original Message-----
> From: Marcelo Lopez Ruiz [mailto:marcelo.lopezruiz@...]
> Sent: Martes 5 de Diciembre de 2000 8:51

There's indeed an option to generate INSERTS, that can be activated from
the step where the BD is requested. One of the options at the window's
bottom allows you to specify an output script.

However, I didn't maintain this facility too well, mainly because ISQL
doesn't have support to insert BLOBs directly from a script and almost all
my BDs have some BLOB or similar field involved, hence the facility wasn't
useful. In reality, the fan of keeping all in scripts is Helen, and as I
remember this option was added due to her suggestion. The ideal solution
would be to modify ISQL to make it to accept BLOBs. The program
has -although deactivated in compile time- the option to write binary BLOBs
in a codified way to allow them to be put in a text file.

Another issue are the internal scripts that are executed to create the DB
and make the migration possible; those are saved in the last step in the
wizard and can be imported again later.

> -----End Original Message-----

Now I want to add my small contribution: Marcelo, what if you could allow
optionally to use f_StrBlob to migrate BLOBs from an script to a db? This
would involve the interested user to install FreeUDFLib and define f_strBlob
without using a prepared insert with parameters.
Another alternative is simply a prepared INSERT where the BLOB is another
parameter. This way, you can read the BLOB from the text file, transform it
(assuming you wrote it as a series of HEX values in readable form, ex:
A3B58900) to its original binary representation and pump it in the db.

C.