We have been using ebase, with FMPro 4.0v3, on Macs for about a year.

We now have a machine that runs Win NT Server 4.0, and would like to 
dedicate it to host our ebase database.

I used NT Server's Services for Macintosh to create an Appleshare 
volume on the Windows machine, then copied all of the ebase files to 
the Windows machine, then opened ebase 4.0v3 on the Windows machine 
and opened ebase_.102. FMPro complains "ebase. 102 could not be 
found."

If I open one of the sample files that delivers with FMPro and share 
it from Win NT, I can connect to it ok from the Mac.

Is this some issue with extension defaults?

Cheryl
Intersex Society of North America
http://www.isna.org

Reply via email to