I'm having a problem using Seagate's Crystal reports distributed by Mas90/200 accessing Btrieve data through native DDF access. The Crystal version is 8.5. However, through a generic Seagate Crystal 8.5, I have no problems accessing the data. I can get the Mas90/200 distribution version to access the data through ODBC after I setup a DSN, so I have a work-around, but the native access fails.
Here's what happens during the "failure". After selecting a DDF, I'm prompted for a Microsfot Access password only, no user name. The data files have no user name access setup what-so-ever, and no password I enter succeeds. Once I cancel, I receive an error message saying something like "File Field.ddf is not a known database type." The odd thing is that when originally browsing for the data files, Btrieve (*.DDFs) is an option for file types. Is the Mas90/200 distribution debilitated in some fashion keeping me from accessing btrieve DDFs, or am I not holding my nose correctly again?
Any help or info is appreciated.
-R
Here's what happens during the "failure". After selecting a DDF, I'm prompted for a Microsfot Access password only, no user name. The data files have no user name access setup what-so-ever, and no password I enter succeeds. Once I cancel, I receive an error message saying something like "File Field.ddf is not a known database type." The odd thing is that when originally browsing for the data files, Btrieve (*.DDFs) is an option for file types. Is the Mas90/200 distribution debilitated in some fashion keeping me from accessing btrieve DDFs, or am I not holding my nose correctly again?
Any help or info is appreciated.
-R