| Subject | RE: [firebird-support] Query works, view doesn't |
|---|---|
| Author | Helen Borrie |
| Post date | 2005-02-25T02:19:47Z |
At 12:39 PM 24/02/2005 -0500, you wrote:
number overflows it by a power of five. If it is BigInt, then it is OK.
If it is a char() or varchar() then it would make sense not to depend on
implicit type conversion but to tidily put this search key in single
quotes. An implicit conversion from BigInt to Char will have unpredictable
results. However, if it is a character type of less than 14, this string
will overflow it anyway.
As to the exception that DBW is returning to you - DBW will be reacting to
an error code sent to it through the API. It is making an inappropriate
reaction to the exception that is occurring - which tells me that the
client connection is reading the wrong message file. This happens when you
have ad hoc mixtures of server and client artifacts around the place.
You don't mention what make and model of server you are using; but to
eliminate these wrong messages, you need to do some searching and version
checking, to eliminate all message files except those that match the
version number of the server -- on client workstations as well as the server.
./heLen
>I forgot to add the query and the view.What is the data type of rxclaimnbr? If it is integer, then this claim
>
>SELECT
>VC.RXCLAIMNBR,VC.CLMSEQNBR,VC.DATESBM,VC.TIMESBM,VC.RVDATESBM,VC.MULTSRC
>CDE,VC.BRNDTRDNME,VC.PRODUCTID,VC.SRVPROVID,VC.SRVPROVNME,VC.PROCESSOR,V
>C.DAYSSUPPLY,VC.DECIMALQTY,VC.USUALNCUST,VC.LABELNAME,VC.AWPUNITCST,VC.R
>XNUMBER,VC.DTEFILLED,VC.PRAUTHNBR,VC.GPINUMBER,VC.PRESCRIBER,VC.PRESLSTN
>ME,VC.PRESFSTNME,VC.CALDISPFEE,VC.APPINGRCST,VC.COSTTYPCDE,
> VC.CLAIMSTS,COALESCE(CC.ACCOUNTID,VC.ACCOUNTID)
>ACCOUNTID,COALESCE(CC.GROUPID,VC.GROUPID)
>GROUPID,COALESCE(CC.CTYPEUCOST,VC.CTYPEUCOST)
>CTYPEUCOST,COALESCE(CC.CALINGRCST,VC.CALINGRCST)
>CALINGRCST,COALESCE(CC.RSPDUEAMT,VC.RSPDUEAMT)
>RSPDUEAMT,COALESCE(CC.RSPPATPAY,VC.RSPPATPAY)
>RSPPATPAY,COALESCE(CC.RSPDISPFEE,VC.RSPDISPFEE)
>RSPDISPFEE,VC.INVOICE,CA.AUDITSTATUS,
> PT.CATEGORY,PT.PATIENTTYPE
>FROM (CLAIMSPAIDREVERSED VC LEFT JOIN (CLAIMAUDIT CA JOIN
>CLAIMCORRECTION CC ON CA.ID=CC.AUDITID)
> ON VC.RXCLAIMNBR=CA.RXCLAIMNBR
> AND VC.CLMSEQNBR=CA.RXCLAIMSEQ
> AND VC.CLAIMSTS=CA.CLAIMSTS)
> LEFT JOIN CHCPATIENTTYPES PT
> ON (VC.ACCOUNTID=PT.CHCCODE
> AND VC.GROUPID=PT.GROUP_ID)
>WHERE
> VC.RXCLAIMNBR=50397285522003
number overflows it by a power of five. If it is BigInt, then it is OK.
If it is a char() or varchar() then it would make sense not to depend on
implicit type conversion but to tidily put this search key in single
quotes. An implicit conversion from BigInt to Char will have unpredictable
results. However, if it is a character type of less than 14, this string
will overflow it anyway.
As to the exception that DBW is returning to you - DBW will be reacting to
an error code sent to it through the API. It is making an inappropriate
reaction to the exception that is occurring - which tells me that the
client connection is reading the wrong message file. This happens when you
have ad hoc mixtures of server and client artifacts around the place.
You don't mention what make and model of server you are using; but to
eliminate these wrong messages, you need to do some searching and version
checking, to eliminate all message files except those that match the
version number of the server -- on client workstations as well as the server.
./heLen