Very bad advice from FileMaker. Delete it all and start over. The files must
remain as .102 files or you are in for some serious script hacking.
Start real simple on NT. Start with the ebase distribution unmodifed by
anyone. Install it on NT. Check that it works. If it does then all you have
to do is copy your real ebase files on top of the demo ones. You should be
opening ebase on NT as the host. Do not attempt to use any of the sharing
mechanisms to get to the files from your Macs. On the Mac open via the host
button on the open dialog box.
If the distribution does not work on NT, you then need to get an NT
consultant in to help you set up accounts and permissions, or do a lot of
reading and experimenting.
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Cheryl
> Chase
> Sent: Monday, January 08, 2001 1:47 PM
> To: [EMAIL PROTECTED]
> Subject: [SUPPORT] Moving from Mac to PC
>
>
> I'm still trying to move my ebase database (which has long
> been running under FMPro 4.03 on the Mac) to Windows NT.
>
> I called Filemaker, and they insisted that I change all of the
> filename extensions to FP3, then open ebase on the Mac in order to
> force it to change all of its internal filename specs, then move it
> to NT. Well that approximately works, but I think that I will never
> see the end of dialog boxes asking me again and again to help FMP
> locate various files.
>
> I don't think that I should have to do this -- isn't that the reason
> that ebase files have extensions of ".102" etc rather than "FP3"?
>
>
> Cheryl
> Cheryl Chase
> Intersex Society of North America
> http://www.isna.org
> "Building a world free of shame, secrecy, and genital mutilation for
> people born with atypical sex anatomy."
>
>
>
