Are you using CF7? If not - and you are using 8 and can convert to the Application.cfc - I would. I know the application level variables are read by my CFC's - I simply address them like #application.xxx# - so - say a function in my CFC runs a DB query - my query line looks like:
CODE
<cfquery datasource="#application.dsn#" name="blarg>
SQL STUFF HERE
</cfquery>
Also, when passing a form to a CFC function - I make the form action an actual page - and invoke the function from that page:
Example:
CODE
<cfform name="thisForm" method="post" action="procPage.cfm">
Then on procPage, I send the whole FORM structure to the CFC:
CODE
<cfinvoke component="cfcs/appUtil.cfc" method="formProc">
<cfinvokeargument name="theForm" value="#FORM#">
</cfinvoke>
Then my function would expect an argument of a type="structure" and handle accordingly.
Does this make sense?
QUOTE(xheartonfire43x @ 4 May, 2009 - 05:25 AM)

QUOTE(apendrag0n3 @ 3 May, 2009 - 07:01 AM)

Not sure what you mean by "application variables don't carry over" - if you are using CF8. I set my dsn in the Application.cfc in and call them from inside my component functions all the time - no need to pass them from inside a form.
I use application.cfm files so maybe that is it, but application.cfm variables don't carry over into cfc's.
This post has been edited by apendrag0n3: 4 May, 2009 - 05:48 AM