![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
The database itself may contain about 400 MB - thus I'd like to avoid running two different runtime solutions, since two separate runtimes will be bigger than a CD-ROM capacity. |
#2
| |||
| |||
|
|
The database itself may contain about 400 MB - thus I'd like to avoid running two different runtime solutions, since two separate runtimes will be bigger than a CD-ROM capacity. This does not work as you must compile your solution on either a Mac for the Mac binded runtime or on a PC for the PC one. Now, I can't imagine why such a distributed solution would be so large, unless you have a lot of imbedded images. If so you could - you should - have a separate folder for those images and have only the reference of the image (its path) into the container field of the record. Maybe this image folder with one file per image could be left open and then be used either by the Mac runtime or the PC one. Just my 2 cents. |
#3
| |||
| |||
|
|
On Sun, 05 Nov 2006 16:10:58 +1300, Helpful Harry wrote: In article <454d15af$0$17258$426a74cc (AT) news (DOT) free.fr>, "Remi-Noel Menegaux" <rnmenegaux (AT) free (DOT) fr> wrote: The database itself may contain about 400 MB - thus I'd like to avoid running two different runtime solutions, since two separate runtimes will be bigger than a CD-ROM capacity. This does not work as you must compile your solution on either a Mac for the Mac binded runtime or on a PC for the PC one. Now, I can't imagine why such a distributed solution would be so large, unless you have a lot of imbedded images. If so you could - you should - have a separate folder for those images and have only the reference of the image (its path) into the container field of the record. Maybe this image folder with one file per image could be left open and then be used either by the Mac runtime or the PC one. Just my 2 cents. You do need two separate runtime application files (and some extras), but your database files themselves are exactly the same for both operating systems, and will still open in FileMaker itself. Yes - it's better documentet within FMP8, while there's not much of an information, concerning the binding key, in FMP7. Is there a chance to catch the binding key from FileMaker directly? |
|
... but unless you're distributing the files to people with a reasonable computer ability, you'll have to include some sort of installer to install the files onto their computer for them. These usually compress the files, but again you'll need a separate installer for each operating system. There are probably some installer creation packages that don't compress the files into a proprietry format and you could then create two installers that copy the files from a single data folder - maybe even a "simple" AppleScript and Windows equivalent. I did not want to install the files at all - I expected to run them from a read-only CD-ROM. |
#4
| |||
| |||
|
|
On Tue, 07 Nov 2006 18:21:46 +1300, Helpful Harry wrote: Yes - it's better documentet within FMP8, while there's not much of an information, concerning the binding key, in FMP7. Is there a chance to catch the binding key from FileMaker directly? I don't know about FileMaker 7 or 8, but in my version the Binder asked you to type in the binding key you wanted - you just have to remember it for next time. So you have to remember both passwords and binding key. |
|
I did not want to install the files at all - I expected to run them from a read-only CD-ROM. It should work fine. You can rename the runtime applications as: "Windows users click here" and "Apple users click here" Unfortunately, the Windows directory is full of garbage - tons of .dll files. I'm not enough of a win person in order to know how their software links work - they seem to be absolute, since they fail after moving directories around: runtime/"Windows users click here" -> runtime/data/FMP.exe I did not observe any problem with the Mac alias "Apple users click here" -> data/FMP, while a relative unix link would be "click here" -> ./data/FMP |
)![]() |
| Thread Tools | |
| Display Modes | |
| |