[FX.php List] Anyone using XSLT anymore?

[Bob Patin]

I'm using 8.5... but what I'm thinking is that I'll just add a field  
to the layout that has the URL to the HTML file... shouldn't add any  
overhead, I woudln't think, since all I'm returning from FileMaker is  
the URL.

I may still return some of the HTML from the database; these reports  
are made up of about 20 chunks of HTML, and when I return the chunks  
the speed is just fine. The problem arises when I have to return all  
20 "chunks" in one long report; I may just output the long report to  
static HTML and leave the little chunks embedded in the database...

At any rate, it's great to see a solution. I'd completely overlooked  
the possibility of using a hybrid of static HTML and database... I  
use it all the time for photos and such, but hadn't thought about it  
in this context...

Best,

Bob Patin
Longterm Solutions
bob at longtermsolutions.com
615-333-6858
http://www.longtermsolutions.com

   CONTACT US VIA INSTANT MESSAGING:
      AIM or iChat: longterm1954
      Yahoo: longterm_solutions
      MSN: tech at longtermsolutions.com
      ICQ: 159333060


On Sep 20, 2006, at 11:04 AM, DC wrote:

> I just remembered that in order for this architectural change to  
> work you must be using a version of the WPE that lets you return  
> the data from a layout that is different from your search layout.  
> otherwise there is no way to stop the HTML field that you want to  
> search from spewing itself into the XML result. so, this scheme  
> wouldn't work in FMP6.
>
> dan
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.iviking.org/pipermail/fx.php_list/attachments/20060920/c4efa3ff/attachment-0001.html