I received an odd error when building up a query.

Here's the server error log.

3/15/2006 5:06:12 PM Re-connection accepted [Client Version: 4.00 User
Name: admin Address: 192.168.137.82 Encrypted: Yes Thread: 812 Session:
23207944]
3/15/2006 5:06:43 PM [ERROR] Engine error [Access violation at address
00509059 in module 'mbdsrvr.exe'. Read of address 00000000] [Client
Version: 4.00 User Name: admin Address: 192.168.137.82 Encrypted: Yes
Request: REQUEST_EXECUTESTMT Thread: 812 Session: 23207944]


What caused it was this.

I was using EMS DBISAM Manager 1.6.0.1 's query builder (I realize this
may end up in their court).

SELECT
  trim(BOTH ' ' from LastName)+', ' + trim(BOTH ' ' from FirstName) + '
' +trim(BOTH ' ' from MiddleName) as "Full Name"
FROM
  tperson


Caused the error from their app.

When putting the same SQL into the TDBISAMQuery, no problem.

I did fine tune the query slightly to this by hand in the Query component.

SELECT
  tperson.LastName,
  tperson.FirstName,
  tperson.MiddleName,
  trim(BOTH ' ' from LastName) + ', ' + trim(BOTH ' ' from FirstName) +
' ' + trim(BOTH ' ' from MiddleName) AS "Full Name"
FROM
  tperson
ORDER BY
  tperson.LastName,
  tperson.FirstName,
  tperson.MiddleName


This worked great.

I pasted back into the DBISAM Manager and this it liked.

Any ideas??   I know they haven't really updated their program in a
while, so it could be that.
I liked the EMS product and am open to other alternatives.

Lance,

<< Any ideas??   I know they haven't really updated their program in a
while, so it could be that. I liked the EMS product and am open to other
alternatives. >>

Actually, 4.0 should be fine working with any 4.x database server, but more
than likely it is related to the version mismatch.  What version of the
database server are you using and what version of DBISAM are you using for
the TDBISAMQuery calls ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

I could give you the lovely line I get from my end users....   "The
latest one"!!    lol  ("oh..  you mean there was something newer than
what I had when I got it in 2003?")

Server is 4.22 build 6.  3 mod's done.  Ports and encryption password.

My D2006 install is same version.

What EMS using??  Couldn't tell you.

I did send a copy of my post to EMS and essentially got a "we will look
at when we work on the next edition" answer.  So no real reason or
confirmation of who's end it is.

Lance



Tim Young [Elevate Software] wrote:
> Lance,
>
> << Any ideas??   I know they haven't really updated their program in a
> while, so it could be that. I liked the EMS product and am open to other
> alternatives. >>
>
> Actually, 4.0 should be fine working with any 4.x database server, but more
> than likely it is related to the version mismatch.  What version of the
> database server are you using and what version of DBISAM are you using for
> the TDBISAMQuery calls ?
>

Lance,

<< I could give you the lovely line I get from my end users....   "The
latest one"!!    lol  ("oh..  you mean there was something newer than
> what I had when I got it in 2003?")

Server is 4.22 build 6.  3 mod's done.  Ports and encryption password.

My D2006 install is same version.

What EMS using??  Couldn't tell you.

I did send a copy of my post to EMS and essentially got a "we will look at
when we work on the next edition" answer.  So no real reason or confirmation
of who's end it is. >>

I doubt that it is EMS's fault unless they modified DBISAM, which I highly
doubt.  It's probably a version mismatch issue, but I can't seem to come up
with a rational explanation for it.  The problem is that the SQL is
basically sent "as-is" to the database server, so the client version should
have little to do with such an error.  And it can't be the actual database
server call, because changing the SQL changes the result (no AV).

Just to confirm, the error is reproducible every time when using EMS with
the first SQL statement that you tried, correct ?  IOW, it's not related to
other people using the database server, etc. ?

--
Tim Young
Elevate Software
www.elevatesoft.com

This is my own development / testing and the only "weird" thing I am
doing is developing and hosting the server under a virtual machine
(VMWare) and the EMS product is on my real / host machine.  The virtual
has a fixed, real IP.

No one else has access to the DB server.

I will try it again to make sure.  I will also take the server and place
it on my real machine and try that as well.

Lance

Tim Young [Elevate Software] wrote:
>
> I doubt that it is EMS's fault unless they modified DBISAM, which I highly
> doubt.  It's probably a version mismatch issue, but I can't seem to come up
> with a rational explanation for it.  The problem is that the SQL is
> basically sent "as-is" to the database server, so the client version should
> have little to do with such an error.  And it can't be the actual database
> server call, because changing the SQL changes the result (no AV).
>
> Just to confirm, the error is reproducible every time when using EMS with
> the first SQL statement that you tried, correct ?  IOW, it's not related to
> other people using the database server, etc. ?
>

Tim,

I confirmed the same behavior by placing the server on my real machine,
creating the database, propagating with sample data and then closing
any applications that have any access to the database.

I launched EMS, registered the host / DB and then created a new query.

I paste the 1st query, same error.

I paste 2nd query, no problem.

=====================================

Complete log.

3/17/2006 11:07:25 AM Starting admin server on all addresses and port
12126 [Server Version: 4.22]
3/17/2006 11:07:25 AM Starting server on all addresses and port 12125
[Server Version: 4.22]
3/17/2006 11:07:34 AM Admin connection accepted [Client Version: 4.22
User Name:  Address: 127.0.0.1 Encrypted: Yes Thread: 4888 Session:
26546184]
3/17/2006 11:07:34 AM Admin login [Client Version: 4.22 User Name: Admin
Address: 127.0.0.1 Encrypted: Yes Thread: 4888 Session: 26546184]
3/17/2006 11:07:34 AM Logout [Client Version: 4.22 User Name: Admin
Address: 127.0.0.1 Encrypted: Yes Thread: 4888 Session: 26546184]
3/17/2006 11:07:34 AM Admin connection closed [Client Version: 4.22 User
Name:  Address: 127.0.0.1 Encrypted: Yes Thread: 4888 Session: 0]
3/17/2006 11:07:34 AM Admin connection accepted [Client Version: 4.22
User Name:  Address: 127.0.0.1 Encrypted: Yes Thread: 4888 Session:
26546184]
3/17/2006 11:07:34 AM Admin login [Client Version: 4.22 User Name: Admin
Address: 127.0.0.1 Encrypted: Yes Thread: 4888 Session: 26546184]
3/17/2006 11:07:34 AM Logout [Client Version: 4.22 User Name: Admin
Address: 127.0.0.1 Encrypted: Yes Thread: 4888 Session: 26546184]
3/17/2006 11:07:34 AM Admin connection closed [Client Version: 4.22 User
Name:  Address: 127.0.0.1 Encrypted: Yes Thread: 4888 Session: 0]
3/17/2006 11:07:34 AM Connection accepted [Client Version: 4.22 User
Name:  Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 43253768]
3/17/2006 11:07:34 AM Login [Client Version: 4.22 User Name: Admin
Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 43253768]
3/17/2006 11:07:36 AM Logout [Client Version: 4.22 User Name: Admin
Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 43253768]
3/17/2006 11:07:36 AM Connection closed [Client Version: 4.22 User Name:
 Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 0]
3/17/2006 11:10:33 AM Connection accepted [Client Version: 4.22 User
Name:  Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 47906824]
3/17/2006 11:10:33 AM Login [Client Version: 4.22 User Name: Admin
Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 47906824]
3/17/2006 11:10:42 AM Logout [Client Version: 4.22 User Name: Admin
Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 47906824]
3/17/2006 11:10:42 AM Connection closed [Client Version: 4.22 User Name:
 Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 0]
3/17/2006 11:13:54 AM Connection accepted [Client Version: 4.00 User
Name:  Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 47906824]
3/17/2006 11:13:54 AM Login [Client Version: 4.00 User Name: Admin
Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 47906824]
3/17/2006 11:13:54 AM Logout [Client Version: 4.00 User Name: Admin
Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 47906824]
3/17/2006 11:13:54 AM Connection closed [Client Version: 4.00 User Name:
 Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 0]
3/17/2006 11:14:35 AM Connection accepted [Client Version: 4.00 User
Name:  Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 47906824]
3/17/2006 11:14:35 AM Login [Client Version: 4.00 User Name: Admin
Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 47906824]
3/17/2006 11:15:27 AM [ERROR] Engine error [Access violation at address
00509059 in module 'mbdsrvr.exe'. Read of address 00000000] [Client
Version: 4.00 User Name: Admin Address: 127.0.0.1 Encrypted: Yes
Request: REQUEST_EXECUTESTMT Thread: 1668 Session: 47906824]
3/17/2006 11:18:51 AM Logout [Client Version: 4.00 User Name: Admin
Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 47906824]
3/17/2006 11:18:51 AM Connection closed [Client Version: 4.00 User Name:
 Address: 127.0.0.1 Encrypted: Yes Thread: 1668 Session: 0]



Tim Young [Elevate Software] wrote:

> I doubt that it is EMS's fault unless they modified DBISAM, which I highly
> doubt.  It's probably a version mismatch issue, but I can't seem to come up
> with a rational explanation for it.  The problem is that the SQL is
> basically sent "as-is" to the database server, so the client version should
> have little to do with such an error.  And it can't be the actual database
> server call, because changing the SQL changes the result (no AV).
>
> Just to confirm, the error is reproducible every time when using EMS with
> the first SQL statement that you tried, correct ?  IOW, it's not related to
> other people using the database server, etc. ?
>

Note:

The DB server never actually displays the error in a dialog itself.
It's only being registered in the server log and is "backfed" to EMS
when executing the query.


Tim Young [Elevate Software] wrote:
 > I doubt that it is EMS's fault unless they modified DBISAM, which I
highly
> doubt.  It's probably a version mismatch issue, but I can't seem to come up
> with a rational explanation for it.  The problem is that the SQL is
> basically sent "as-is" to the database server, so the client version should
> have little to do with such an error.  And it can't be the actual database
> server call, because changing the SQL changes the result (no AV).
>
> Just to confirm, the error is reproducible every time when using EMS with
> the first SQL statement that you tried, correct ?  IOW, it's not related to
> other people using the database server, etc. ?
>

Lance,

<< I confirmed the same behavior by placing the server on my real machine,
creating the database, propagating with sample data and then closingany
applications that have any access to the database.

I launched EMS, registered the host / DB and then created a new query.

I paste the 1st query, same error.

I paste 2nd query, no problem. >>

Okay.  I'll try it out here and see what I get.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim!



Tim Young [Elevate Software] wrote:
> Lance,
>
> << I confirmed the same behavior by placing the server on my real machine,
> creating the database, propagating with sample data and then closingany
> applications that have any access to the database.
>
>  I launched EMS, registered the host / DB and then created a new query.
>
>  I paste the 1st query, same error.
>
>  I paste 2nd query, no problem. >>
>
> Okay.  I'll try it out here and see what I get.
>