Thanks Gary for your help... I will look at changing the Field Names (I
think this will be easier in the end..!)
Gary Menzel wrote:
I personally wouldn't name the fields with the name of the database -
naming the table should be enough (but it would depend on which DB you
are using and if you were intending to create joins between the two
databases). Even so, you would be able to avoid name clashes by using
alias' for the tables that have the same field names.
But...
I am assuming you are wanting to write "generic" code that can be used
across multiple databases. So - why not do it that way - create
multiple databases with the same schema - and then simply swap DSN's ?
Then you can create up one set of SQL scripts to create your schema,
and a bunch of CFC's that manipulate the database, and just have
different databases with the same schema (initialising the instances
of the CFC's with the DSN).
HOWEVER - this does not address the issue that appears to be happening
- and that is the apparently "missing" vars in the Applicaiton scope.
I am not sure why you cant reference the variables in the Application
scope if you can readily see them in the <CFDUMP>.
Regards,
Gary
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
