ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Crystal Reports, ODBC & Access >> Crystal Reports General Issues >> mkiclass file not visible in Crystal Reports
http://www.istechforum.com/YaBB.pl?num=1241713352

Message started by pmoser on 05/07/09 at 09:22:32

Title: mkiclass file not visible in Crystal Reports
Post by pmoser on 05/07/09 at 09:22:32

I have a Crystal Report that used to look at the BKAP.CHK.INVNUM field in the BKAPCHKH file for the Invoice Number. I know that the real invoice number was moved to the MKICLASS file but the file does not show up in Crystal Reports when I try to add it to the report (direct or ODBC). I CAN open the file in Maintain Database in EVO. One strange thing I see in Maintain Database is in the File Lookup screen, the "FD Name" field shows "MKECLASS" for the MKICLASS filename.

Title: Re: mkiclass file not visible in Crystal Reports
Post by GasGiant on 05/07/09 at 09:29:11

You need to remake your ODBC DDFs with the ODBCDDF.RUN program. That needs to be rerun each time new tables are added to DBA/Evo or your ODBC connection will not be able to find them.

Title: Re: mkiclass file not visible in Crystal Reports
Post by pmoser on 05/07/09 at 11:46:53

I restarted CR and the file is there now.

Now I've got a different problem. I'm trying to link BKAP.CHK.INVNUM to MKECLASS.NUM and I get a data mismatch error since BKAP.CHK.INVNUM is a string and MKECLASS.NUM is a number. Is there any way to link these?

Title: Re: mkiclass file not visible in Crystal Reports
Post by kevind on 05/08/09 at 12:22:18

One way to link different types for Crystal is to create a view of your data in Pervasive.
This makes the linked table look like 1 table to CR.

For example:
drop view CHKTEST;
create view CHKTEST
(
bkap_chk_chkdte,
bkap_chk_invnum,
mkeclass_num,
mkeclass_desc,
mkeclass_active
)
AS
select bkap_chk_chkdte, bkap_chk_invnum, mkeclass_num, mkeclass_desc, mkeclass_active
from bkapchkh a, mkeclass b
where a.bkap_chk_invnum = convert(b.mkeclass_num, SQL_VARCHAR);

This view, called CHKTEST, links bkap_chk_invnum (a VARCHAR) to mkeclass_num (a DOUBLE) by
converting the DOUBLE to a VARCHAR and then performing a link.

In CR, you would then select the table called CHKTEST instead of mkeclass and bkapchkh. You may need to
add additional fields into this view from bkapchkh so that you can put them on your report. A view looks like 1 table
to CR. Pervasive takes care of the linking at the server. If you limit your selection criteria in CR to only records after
a given date or date range, it will run faster.

Hope this helps.