At 3:11 PM -0500 1/9/01, Walt Daniels wrote:
>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.
Yes, I knew that I didn't want to do this as a solution, but decided
to try it as an experiment. It seems to have eliminated the
possibility that the problem was due to NT permissions.
>
>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.
I already tried downloading the distribution version of ebase in
order to do this experiment. Unfortunately, the current distribution
is 1.03, which requires FMPro 5. I have a single license for FMPro 5,
and it opened the distribution 1.03 files OK. Because I only have a
single license (waiting for answer on request for FileMaker
donation), I can't test sharing.
Then I went back, copied my live 1.02 files to NT again, and tried to
open them on NT, in order to observe the failure again. But this
time, it didn't fail.
I don't understand what made the difference. What's changed? I have
installed FMPro 5, I have installed the distribution version of ebase
1.03, and I have installed a somewhat newer copy of the live 1.02
files (because we've been entering data daily). I have logged out and
logged back in to NT as administrator, but not rebooted. I have
created a normal NT user.
>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.
Yes, I do know better than to open the files on a shared filesystem.
It's working now, but I would feel better about starting to host my
data on NT if I understood what had been failing.
Cheryl
