Ok I can now connect, but now in MSAccess I see no tables?
 
Again is there a step by step guide to connect using ODBC.
 
I have a setup other ODBC connections before.

Ok,
 
I am now getting the error 35 again.  My ".B" are in the default\ directory.  Is this where they are suppose to be?  Is there any way I can get a step by step instructions on how to setup the ODBC connection.
 
thanks
George

Well... As you might guess, that error means that btrieve cannot access the directory with the data files. This could be for a number of reasons:
 
1. Maybe you don't have the drive mapped or connected? Can you use windows explorer to go to where the files are located and see them?
2. Maybe something is wrong with your DDF files? Have you tried rerunning ODBCDDF?
   2a. It's possible that your DDF files are pointing to a directory which doesn't actually exist. Maybe you changed drive letters or something?
3. Maybe there is a server or workstation problem? Can you successfully run evo/dba from the machine in question?

Error 5 is a Duplicate Key - you can typically click OK and generate the DDFs and operate with no problem.
 
Error 35 is a Directory error - that is different and relates to drive maps and permissions.

your version of Crystal Report has nothing to do with either btrieve error. every report keeps it's information of how it was connecting to the database when it was first designed. if that connection doesn't exist, or has changed, then hence the btrieve 35 error.
how to fix, depends on the connection your report is using. and as such, if more than one person runs the same report, then they have to have identical path that the report was using.
 
if you want, i can remote your computer and we can fix your btrieve error situation with your Crystal Reports.
email me, or call, davemeng@earthlink.net or 760-832-2536