>>Sounds like one of the Crystl DLLs did not get installed properly for some reason. Look in the developer help file to find out which DLL is needed for DBF access and reinstall it.
>
>Craig, this was *exactly* the problem. The reason why it didn't appear to work the first time was that the user had to copy p2bxbse.dll to C:\Windows\Crystal *in addition to* the same file shipped with the app. Copying to C:\Windows\Crystal isn't optional; apparently the user didn't think that one would "matter"
.
>
Della, why is the -user- copying anything at all - that's part of what the Setup is supposed to do! If you use the VSI or another product like the InstallShield versions that support the Windows Installer, there is a working MSM for Crystal 8.0 available at InstallSite that places the runtime components in place, with the exception of any restricted distribution items like CRAXDRT.DLL that require a separate developer license to distribute. VSI is far more capable than Setup Wizard, there's an MSM for VFP6 SP4 out, and there are lots of capabilities for customizing the VSI setup, including the ORCA MSM editor (incredibly poorly documented, but easy enough to figure out if you really read the VSI docs to discover how the MSM is organized.) InstallShield now supports the Windows Installer technology in both the current version of InstallShield Express and the new upgraded version of InstallShield Pro, and with the exception of managing the installation of prerequisite components, directing installation to directories other than CSIDLs, or safely adding executables to a transactional install, there's little need for the Pro version.
