According to the Pervasive.SQL V8 documentation, the "type" parameter of the
CONVERT function is an ODBC type.

When doing a CONVERT, is the kernel executing the function, or is ODBC?

I'm having a bit of a problem with a CONVERT(string, SQL_DATE) on a
Pervasive 2000 (Netware) database. The function works fine on my Developer's
Workgroup V8, but in a production Netware environment, it's crashing with a
syntax error. Any enlightenment would be appreciated.

Any CONVERT would be done by the SQL engine.
The MicroKernels only concern with data types is when it is sorting a
key. To it, bytes are bytes and it does not do any conversions.

If it works with V8 but fails with 2000 (fcs, sp1, sp2)? you may wish
to upgrade to Pervasive.SQL 2000i sp4 plus hot fix.
http://www.pervasive.com/support/updates/

Which resolves specifically:
35065 Rather unconventional view of "CREATE VIEW MYVIEW AS SELECT
CONVERT('1900-01-01', SQL_DATE)" caused the engine to GPF.
which looks to me like it should fix your convert statement.

Leonard

On Wed, 14 Jan 2004 01:26:23 GMT, "MyndPhlyp" <nobody (AT) home (DOT) now> wrote:

"Leonard" <lharvey (AT) austin (DOT) rr.com> wrote

There is a possibility I have my version wrong. It might be 2000i w/ SP3.
For some reason, SP3 sticks in my mynd. If FCS, SP1 and SP2 are the only
options for 2000, it must be 2000i I'm playing with. I'll have to check next
time I'm on-site.

The bug notice you quoted sounds like it hits around the fringes. I'm not
GPF'ing; only generating a syntax error. Still, it's worth investigating
with the application of the latest available SP.

Upgrading isn't an option, unfortunately. The Pervasive software is part of
a bundled license from yet another vendor. Even applying a future SP drives
their so-called tech support into a frenzy.

Thanx for the reply. I'll spend a little time playing around with the
CONVERT on-site and, if I can't seem to work around the problem, install SP4
(assuming I was initially wrong and they are using 2000i).

"Leonard" <lharvey (AT) austin (DOT) rr.com> wrote

It turns out SP4 was the fix. I found the bug you referenced in the hotfix
documentation, but thought I'd give just SP4 a try initially (after
double-checking the client software on the workstation, of course).

I have the hotfixes on standby in case something specific shows up, but
everything appears to be running okay at the moment.

Thanx again.