Back in April I had run into problems getting FMSA 9 to install properly on a server running the 64-bit version of Windows. This evening I was finally able to take some time and try this again -- and this time, success!!!
Thanks to some suggestions from FileMaker Addict readers, I found a way to get IIS to run in such a way that 32-bit ISAPI filters (such as the FileMaker Web Publishing Engine) run properly. For details, visit http://support.microsoft.com/kb/894435. Essentially, this involves running a command from the command line ("cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1"), which enables 32-bit mode.
But that wasn't all that was involved. I also had to manually add the FMI Web Publishing Engine to the list of Web Publishing Extensions, and add PHP as well. To do so:
1. I opened up the IIS Manager, and selected the Web Service Extensions folder.
2. Under Tasks, I clicked Add A New Web Service Extension.
3. For the extension name, I entered: FMI Web Publishing Engine
4. For required files, I added: C:\Program Files (x86)\FileMaker\FileMaker Server\Web Publishing\publishing-engine\web-server-support\iis\isapi_redirect.dll
I did the same for PHP -- except that the Extension Name is "PHP" and the required file is located here: C:\Program Files (x86)\FileMaker\FileMaker Server\Web Publishing\publishing-engine\php\php5isapi.dll
And with that, everything started working -- Instant Web Publishing, PHP Custom Web Publishing, and XSLT Custom Web Publishing.
FileMaker Addict Has Moved!
Friday, August 29, 2008
Monday, August 04, 2008
Two More For the FileMaker Wishlist
I'm processing a very large batch file for a client this morning, and it is going very, very slowly. That got me thinking about how, with a few new FileMaker Pro features, this file might have been easier to process. So here are two new features that I'd like to see in a future release of FileMaker:
* Replace Multiple Field Contents: Wouldn't it be great if you could replace the contents of multiple fields at the same time, instead of having to perform multiple Replace Field Contents? I figure that FileMaker is having to "touch" the records anyway -- why not have it make all of the changes at the same time?
* Truncate Table: This would allow you to quickly and easily delete all of the records in a table. You can do this in most SQL databases. The reason that it is so fast is that the process also simply drops any indexes on the table as well -- so it doesn't have to update the index as each record is deleted.
I'm going to swing over to the Secret Weapon Labs FileMaker Wishlist and add these!
* Replace Multiple Field Contents: Wouldn't it be great if you could replace the contents of multiple fields at the same time, instead of having to perform multiple Replace Field Contents? I figure that FileMaker is having to "touch" the records anyway -- why not have it make all of the changes at the same time?
* Truncate Table: This would allow you to quickly and easily delete all of the records in a table. You can do this in most SQL databases. The reason that it is so fast is that the process also simply drops any indexes on the table as well -- so it doesn't have to update the index as each record is deleted.
I'm going to swing over to the Secret Weapon Labs FileMaker Wishlist and add these!
Sunday, August 03, 2008
Understanding Exact Matches
There are two very similar -- and therefore, somewhat confusing -- exact match operators available when specifying find criteria in FileMaker Pro. I've had a lot of FileMaker users ask me what the difference between them is, so here is a brief explanaition...
The first operator, which is the equal sign ("="), is used to find exact matches on whole words. For example, a standard search in a Company Name field for Statistic will find Advanced Statistic Experts and Statistical Analysis Inc (because, by default, FileMaker performs a full text "begins with" search). However, by adding the "=" symbol to the search (=Statistic), FileMaker finds Advanced Statistic Experts, but does not find Statistical Analysis Inc.
The second operator, which consists of two equals signs ("=="), is used to find exact field contents. For example, a search in a Company Name fields for ==Doe Design Concepts Inc will find Doe Design Concepts Inc but not Doe Design Concepts Incorporated.
So there you go. A subtle, yet very important, difference.
Note that either of the two exact match operators can be used to find fields that are empty. To do so, simply search for "=" or "==" and FileMaker will locate records where the field is empty. (Also note that by "empty" we mean really empty. The field cannot have anything in it, not even a single space.)
Want to find fields that are not empty? Either do an omit search for "=" or "==" or do a search using the "*" operator.
The first operator, which is the equal sign ("="), is used to find exact matches on whole words. For example, a standard search in a Company Name field for Statistic will find Advanced Statistic Experts and Statistical Analysis Inc (because, by default, FileMaker performs a full text "begins with" search). However, by adding the "=" symbol to the search (=Statistic), FileMaker finds Advanced Statistic Experts, but does not find Statistical Analysis Inc.
The second operator, which consists of two equals signs ("=="), is used to find exact field contents. For example, a search in a Company Name fields for ==Doe Design Concepts Inc will find Doe Design Concepts Inc but not Doe Design Concepts Incorporated.
So there you go. A subtle, yet very important, difference.
Note that either of the two exact match operators can be used to find fields that are empty. To do so, simply search for "=" or "==" and FileMaker will locate records where the field is empty. (Also note that by "empty" we mean really empty. The field cannot have anything in it, not even a single space.)
Want to find fields that are not empty? Either do an omit search for "=" or "==" or do a search using the "*" operator.
Subscribe to:
Posts (Atom)
