Lasso 7.1.1 and FMP6 converter

[Xas]

I have been toying with FMP6 CDML converter from Lasso since Lasso people claim that Lasso 7.1.1 is compatible with FMP7 Server Advanced. So far, I have had enormous trouble fetching data from the databases unless I use [iNLINE] [iNLINE] statements. Lasso documents that they are deprecating non-inline statements but are still compatible with CDML converted to LDML code. Sounds nice, but when I select 'Classic Lasso' Support in the Lasso Admin Setup, I get an Internal Server Error from MAC OSX/Apache 1.2. Lasso tech support is attentive even with this eval version I have, but they do not answer my questions as I would expect. Maybe it has something to do with email vs voice. Since I have 1000 CDML pages it would be nice to do a slam dunk conversion (using the Lasso CDML-->LDML converter) and then go back and little by little convert to more secure [iNLINE] code.

[ibiubu]

I am probably looking at going the Lasso route. I have 150 CDML pages, and don't want to switch over to XML to use FM7. I am hoping to be able to switch over to Lasso and then covert my CDML tags to LDML tags.

Have you actually been running Lasso with FM7? Having any success?

Larry

[Xas]

Still waiting for the Server 7 Advanced to hit my door. Purchasing Dept. claims to have ordered it. Until then I discovered (I admit - after I figured it out myself), the tech support dude at Lasso told me I was right - you have to name lasso command files with lasso extension (filename.lasso, instead of previous filename.html, Note: this is for any file that issues Lasso commands), THEN IT WORKS! I can pull data out of FMP6 using Lasso 7.1.1. This cool since I can work on my conversion errors and once they are solved it should work seamlessly with 7 Advanced. BUT, I can only get [iNLINE] statments to work. External LDML calls are still dead. I haven't had much time with it lately, but after I get back from a well-needed 10 day vacation I plan on busting it out quickly. My 30 day eval is coming to and end soon however for Lasso. Let you know how it goes.

[ibiubu]

So you are saying that with the new lasso, all old HTML files that were converted over from CDML to LDML have to have the extension changed from .html to .lasso?

Sounds a bit odd to me.

And since I dont quite know what you are referring to when talking about [iNLINE] then my current CDML probably does not use it. So if I am using standard CDML tags throughout my HTML pages such as [FMP-If:] and [FMP-Field:] and [FMP-Image:] does this mean that if I try to convert them to LDML for lasso then they will not work because they are not [iNLINE]?

Larry

[Xas]

That's what I am in the midst of trying to figure out. Since I am on vacation until 10/19 I won't get a chance to move on this until I return. What I am saying is that the Lasso support tech told me that the Lasso server (out of the box) is not configured to parse html files with action.lasso commands. You CAN configure it to - but he said a converted CDML --> LDML file SHOULD have a lasso suffix in order for the Lasso server to parse the newly converted files properly. And he was right. A test file he sent me (with INLINE lasso commands) didn't work if it was named test.html, it had to be renamed to test.lasso and it dumped data from my FMP6 database. This was something I overlooked. He also said Lasso WILL work WITHOUT INLINE commands but this is not safe. Users can browse regular CDML or LDML files without INLINE commands and learn the inner schema of your database. INLINES are totally invisible to the browser since they are server side only. That is pretty cool. I am going to rewrite my code to do this after I get the monster I have created up and running after a quick conversion. So far it has not been easy. A quick conversion from CDML-->LDML yields nothing so far so I have some bug searching to do, Like renaming the file to have a lasso suffix, etc... Lasso tech recommended against configuring the server to use html extensions for processing lasso commands. Let you know how it goes.