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.

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.