Tim,

I picked up the upgrade to DeZign for Databases V5.  I had 4 because it
supported DBISAM 3/4.   V5 supports EDB v1 (and dropped DBISAM 3.x which no
longer affects me).

I was able to reverse engineer an existing DB into DeZign which is great.

I then decided to do an export to create the SQL for the creation/drop of my
DB and compare with my script vs what DeZign did.

First "major" thing was that it was lacking the table version and some of
the goodies that seem consistant and specific to EDB.  Considering DeZign
supports multiple database targets and that table versioning is not
supported by many DB's, I could accept that.

Thankfully, DeZign provides a special Table option that puts the contents of
the memo at the end of the table creation statement.

So I had to add:

                    VERSION 3.01
                    UNENCRYPTED
                    INDEX PAGE SIZE 4096
                    BLOB BLOCK SIZE 512
                    MAX ROW BUFFER SIZE 32768
                    MAX INDEX BUFFER SIZE 65536
                    MAX BLOB BUFFER SIZE 32768

No biggie.

However, one of the things that their generated code did, that created a
problem was putting a single qoute around CURRENT_GUID and
CURRENT_TIMESTAMP.

When I compared what I had, which was reverse-engineered from your tool, to
the DeZign, theirs had 'CURRENT_GUID' and 'CURRENT_TIMESTAMP'.

I guess I need to ask who's the "guilty" party?

On a seperate note, they didn't seem to support adding COLLATE "ANSI" to the
columns.   Any issues to be expected if I don't massage their output?

Same with indexes, where they don't have COLLATE "ANSI_CI".  Any issues to
be expected if I don't massage their output.

While I would love to purely be able to take DeZign's output and bring it in
completely without massaging the SQL, my expectations are that I still may
need to do so.  It just would be nice to minimize that.

Lance

Lance,

<< I guess I need to ask who's the "guilty" party? >>

They are.  It sounds like they're using the old DBISAM way of specifying
DEFAULT expressions as strings instead of as normal expressions.  The only
thing that should be enclosed in single quotes are string constants.

<< On a seperate note, they didn't seem to support adding COLLATE "ANSI" to
the columns.   Any issues to be expected if I don't massage their output? >>

The default collation is ANSI, so no.

<< Same with indexes, where they don't have COLLATE "ANSI_CI".  Any issues
to be expected if I don't massage their output. >>

Nope, same as above.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim,

Rick there was very quick to respond and made several typo fixes and other
adjustments for EDB.

I will remind him regarding the collation though as that may be a needed
feature.

Lance


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:E3AEA35B-FA1D-4090-B866-E854E0370A28@news.elevatesoft.com...
> Lance,
>
> << I guess I need to ask who's the "guilty" party? >>
>
> They are.  It sounds like they're using the old DBISAM way of
> specifying DEFAULT expressions as strings instead of as normal
> expressions.  The only thing that should be enclosed in single quotes are
> string constants.
>
> << On a seperate note, they didn't seem to support adding COLLATE "ANSI"
> to the columns.   Any issues to be expected if I don't massage their
> output? >>
>
> The default collation is ANSI, so no.
>
> << Same with indexes, where they don't have COLLATE "ANSI_CI".  Any issues
> to be expected if I don't massage their output. >>
>
> Nope, same as above.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Lance,

<< Rick there was very quick to respond and made several typo fixes and
other adjustments for EDB. >>

Cool.  From what I can gather, they run a tight ship over there and do a
great job of responding to customers.

<< I will remind him regarding the collation though as that may be a needed
feature. >>

Thanks.

--
Tim Young
Elevate Software
www.elevatesoft.com