Using BDE 5.x, I have a query which sucessfully runs against 98%
of our datasets.  For some reason, it gives an Access Violation
with some datasets.  In my WHERE clause, I have
alias.fieldA = alias.fieldB  and this produces an AV in the App, Database Desktop, and DB Explorer.  If I change it to
alias.fieldB = alias.fieldA it works.  Is there any explaination
for this?
I would much appreciate any thoughts, suggestions... I'm really
pulling my hair out!
Thanks a MB!

--
Bill
(TeamB cannot answer questions received via email)

We are using Foxpro 2.6 databases.  The application is used by
1000+ companies.  We have had < 10 reported AV's.  

One of my queries which fails with a problematic dataset is:

SELECT
 cross.acctval                       AS acctval,
 action.ALABEL                       AS SLAType,
 family.pfdesc                       AS family,
 type.ptdesc                         AS type,
 CAST('---' AS CHAR(30))             AS desc,
 CAST('-' AS CHAR(1))                AS dabb,
 CAST(0 AS NUMERIC(10,0))            AS comp,
 CAST(0 AS NUMERIC(15,0))            AS lenxx,
 feat.chg                            AS xasdf,
 CAST("" AS CHAR(1))                 AS CONNIND,
 CAST(0 AS SMALLINT)                 AS FCONNCNT,
 CAST(0 AS SMALLINT)                 AS PCONNCNT

FROM
 ':Alias_Local:cross'   cross,
 ':Alias_Local:action'  action,
 ':Alias_Local:family'  family,
 ':Alias_Local:type'    type,
 ':Alias_CD:feat'       feat

WHERE
 feat.svcarrid =action.slval AND
 cross.aggrhpid = action.aggrhpid AND
 feat.pfamfk = family.pfamid AND
 CAST(feat.ptypfk AS SMALLINT) = CAST(type.ptypeid AS SMALLINT)

To make this work with my problematic datasets, I change my
WHERE clause to look like:

David R.

 Let me try again...
We are using Foxpro 2.6 databases.  The application is used by
1000+ companies.  We have had < 10 reported AV's.
One of my queries which fails with a problematic dataset is:
SELECT
 cross.acctval   AS acctval,
 action.ALABEL   AS SLAType,

--
Bill
(TeamB cannot answer questions received via email)

--
Bill
(TeamB cannot answer questions received via email)

David R.

The thing is, we do not write to FoxPro tables.  We get our datafeed from another system and we only use the FoxPro tables as read only...we just query against them.  When the BDE runs a query and builds the temp file, it is my understanding that it creates a paradox file.  Is there any point of me converting these tables to paradox and testing the query?

Thanks again.
Neil.

"David R. Robinson" <ibinst...@mail.com> wrote:

You should be able to use datapump to move the data from one database to
another.  As far as your problem goes, I'm in the same boat as Bill
(never used FoxPro tables).  It may be time to call support back.

David R.

I am going to export my foxpro tables into Paradox
and try my query again.  If it still fails I will phone
support.

I really appreciate your help!

Thanks.
Neil.

"David R. Robinson" <ibinst...@mail.com> wrote:

--
Bill
(TeamB cannot answer questions received via email)

I ported the data over from Foxpro tables to dbase tables.  
I ran my query and got the same Access Violation.  

Any suggestions?

Thanks..

"Bill Todd \(TeamB\)" <bill.nos...@dbginc.com> wrote:

What is your DB ?

Jean-Michel

"Neil" <nasrog...@hotmail.com> a crit dans le message news:
3bfa56c7$1_2@dnews...

Initially I was querying against FoxPro databases,...then I ported the data to dBase format...and then to Paradox.  The query failed with all.