> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com] On

Behalf Of Hans

> Sent: Wednesday, July 26, 2006 4:10 PM
> To: IBObjects@yahoogroups.com
> Subject: Re: [IBO] TIBOTable.FindNearest
>
>
> One approach
>
> Replacing the blanks with undescores could be done in all source modules

at

> once with a routine like GReplace.exe
>

Actually, it's not safe to do that in every case because some instances may
not be actual field names, but column headings or something else that'll get
printed.

And even GReplace doesn't address issues like column names like 'Date' or
'Time', or that start with numbers. I'm afraid I'm pretty much going to
have to comb through the entire body of code.

> Export the database SQL (only) and apply same changes, then recreate
> database.
>

The data is in Paradox tables, so the database gets created by a converter
program that I've written to deal with various inconsistencies in the data
(such as null fields where they aren't allowed in FB). I'd just mark it up
to do the name change there. It's the application that's the issue.

> I found that worked better in the long run, than getting totally stuck.
>

There's no time (or money, which is much the same) for this right now.
If the IBO folks can't fix this, it may be I'll have to decide whether to
soldier on or revisit MSDE and dbGo in order to meet the deadline.


Michael D. Spence
Mockingbird Data Systems, Inc.