SmartPill can be installed to work with both FileMaker Server and the Web Publishing Engine (WPE).
Here are the installation paths for each. Both examples assume that FileMaker is installed on the "C:" drive.
FileMaker Server:
Install the PHP.fmx file and the "PHP Support" folder here: C:\Program Files\FileMaker\FileMaker Server\Extensions\Plugins
Install the php5ts.dll file here (same folder that contains the fmserver.exe file): C:\Program Files\FileMaker\FileMaker Server
WPE:
Install the PHP.fmx file and the "PHP Support" folder here: C:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\wpc\Plugins
Install the php5ts.dll file here (same folder that contains the fmserver.exe file): C:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\wpc
Server 2003 Installation Paths For SmartPill Version 1.0.0
SmartPill can be installed to work with both FileMaker Server and the Web Publishing Engine (WPE).
Here are the installation paths for each. Both examples assume that FileMaker is installed on the "C:" drive.
FileMaker Server:
Install the PHP.fmx file and the "PHP Support" folder here:
C:\Program Files\FileMaker\FileMaker Server\Extensions\PluginsInstall the php5ts.dll file here (same folder that contains the fmserver.exe file):
C:\Program Files\FileMaker\FileMaker ServerWPE:
Install the PHP.fmx file and the "PHP Support" folder here:
C:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\wpc\PluginsInstall the php5ts.dll file here (same folder that contains the fmserver.exe file):
C:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\wpcRegards,
Micah
msvcr71.dll
Hi-
Does the msvcr71.dll file also need to go in the C:\Program Files\FileMaker\FileMaker Server directory for Server 2003?
Colin
msvcr71.dll
That's correct.
If anyone is wondering what the msvcr71.dll file is, please look here for more detail: http://www.scodigo.com/forums/post/111.
Also note that we have fixed this in our development version and will be including the fix in our next release.
Regards,
Micah