>>I should mention that I'm using the stand-alone ebase,
>>not FileMaker. Is the stand-alone version pickier
>>than FileMaker about which files it will use?
>
>Bingo! Although the document file format is the same, the ebase
>runtime application is different on the two platforms. You should
>download a Mac version of ebase from the web site, replace the
>Windows application ebase.exe with the Mac runtime ebase.102. All the
>other files you download are empty data files and you can discard
>them.
Er, yes, I know the runtime application is different; I have fully
functional copies of the ebase runtime on both Mac and Windows. But when I
take the .103 files that I customized under Windows (not the .EXE or .DLLs,
which of course won't work on the Mac) and try to open the Mac runtime with
those files instead of the .103 files that came with it, it says the files
are not part of this solution.
Are the two runtime programs similar enough that they can read each other's
files, or is the full version of FileMaker Pro required on both platforms
to make this work? Are other people able to get the Mac runtime to open
the Windows runtime's files? If so, how do you do it? Do I need the .DLL
files as well to get the Windows .103 files to open?
Thanks again...
Ben Stallings, COO
World Population Balance
------------------
Reminder to each recipient: To change your list account preferences, go to
http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address
you used to subscribe to the ebase support list:: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
---------------------------------------------------------------------
ebase - Relationship Management for Nonprofits, http://www.ebase.org
---------------------------------------------------------------------
