I get an error on the live server that doesn't appear on my local server.

Why would my UDF work just fine on my local server machine but give the following error on the live hosted server?
***********************

Invalid parser construct found on line 4 at position 12. ColdFusion was looking at the following text:qLocationInfoToStructure

Invalid expression format. The usual cause is an error in the expression structure.

The last successfully parsed CFML construct was a CFSET tag occupying document position (3:1) to (3:6)

***********************
Here is the cfset tag it mentions:

1.<cffunction name="locationQuickInfoQuery" returntype="query">
2.<cfargument required="true" name="location" type="string">
3.<cfset var qLocationInfoToStructure = "">
***********************

I can't even duplicate the error to begin debugging it. Any ideas? Does anyone need to see more of the code?

Nathan

I don't see a problem. While CF does its best to give you the real cause of the error, sometimes the line number being flagged is not correct. Try doing some cfdumps inside your function(s) to confirm that the problem isn't somewhere else.

I fixed the previous problem by just taking the code out of the function tags and using the code in a cfinclude. It's not as elegant but...

Now I'm getting a problem with a login sequence. The login sequence works fine in all browsers but Explorer 6 (big surprise, I hate that piece of junk (actually piece of ****)) browser.

I have the login code in the App template and it simply uses some CFIF blocks to check for FORM inputs and session variables.

The form I use is the standard compliant form structure for XHTML. Example: It uses <legend>'s <dt>'s and <labels>'s.

Why would the code work in one browser but not another one?

The login check template simply uses a CGI.SCRIPT_NAME redirect once the session structures are filled but IE just redisplays the login form again and again and again.


Sorry so long of a question...

Nathan

If you do a CFDUMP of the FORM scope on the action page, it may help you determine which field(s) are causing the problem.