jgreenlee

Hey, thanks for your response. when you say, "As with IWP, there is a learning curve with CWP..." I must comment that I think the whole bleedin' idea of IWP is that there is NO learning curve.. thats its problem. What you see is apparently what you get. No frills, Do not pass GO... Garbage in, Garbage out sort of thing... (sigh!) So I guess really the only solution is to go to CWP... which I'm going to do.. but boy its not easy finding documentation on it! I tried using the CDML module that FileMaker provides.. but the examples won't work with 6.0 .. only 5.5 for some reason... How did you go about finding docs for the "learning curve"? I have a fair amount of Cold Fusion experience.. I can't imagine CDML would be a whole lot different would it? Jeff

Hi! I don't have an answer for you.. I just wanted to commiserate, because we have the same dilemma! Its really annoyoing!!! I'm sure no one has answered this because they are tired of stating that IWP is "very Limited". My own conclusion so far is that you simply can't use Portals for Web Companion if you are using IWP. I'm speculating but I assume thats because IWP just simply can't access 2 database files at a time. If the field in question does not belong in the record you are entering it can't embed a whole different form inside the main form that puts data that "other" database. You may notice it might display data, you just can't edit it. Jeff

Hi, I have recently converted our databases over to IWP using FMPro 6. In one of the primary DB's there is one particular record that displays fine in FM but produces an IE error (see attached) when I try to access that particular record from a browser. I can navigate to any of the other records just fine. It's just this one record! I get the same error when I try to Search or Sort. As an expiriment I tried setting up Web Companion so it would sort the records before it reaches the Browser... I got all the records but once again, when I navigated to that one record.. Ouch! Unsorted, this "bad" record is the last one, so I'm wondering if there is some sort of indexing problem or something that Web Companion can't handle when it generates the HTML??? Again it produces no problem whatsoever in FM. I keep looking at the DB in Table view and I can't detect any sort of Key violation or thing like that. Anyone have any ideas what might be hapening here? Once again I will attempt to post an image of the error. You may notice the token in the URL that refers to the number of the record. when I play with it, it appears to by one less the the actual record number. (I assume that's because Javascript, or what ever its using is 0 based.) Jeff