Ask a Question related to Coldfusion Database Access, Design and Development.
-
indnajns #1
Upgrade blew up code
My host's server crashed a couple months ago. Without warning, they decided to
upgrade to 7.0 while salvaging from this crash. The WORKING code I had was
written a couple years ago for CF 5.0. Unbeknownst to me, the host had already
upgraded to CF6.1 at some point. I didn't know nor care about that upgrade
because it didn't break my code. But this round, going to 7.0 DID kill my
code. SImple things like commas in dollar amount fields now throw errors. And
code that uses CFFile throws errors. As well, a couple of queries now give
syntax errors. Anybody know of a good document that explains the new syntax of
7.0? And please define the "MX" phenomenon. Like I said, it was working code,
worked for years, until it met CF7.0.
indnajns Guest
-
Why doesn't the Code Completion occur in FlexBuilder IDEwhen source code is in an external file?
I am seperating my .as from the MXML by using the following in my file.mxml: <mx:Script source="file.as"> When I edit file.as, the code... -
Breezy, it blew away my system. Who should be shot?
I tried the live CD, looked good!! I confirmed my hardware compatibility. Looked good! I installed it. Looked BAD!! 1. It prompted for my... -
Custom control fires event but ignores some code in the code behind file
I do not quite understand the question. I will merely point out that most programming problems happen for a reason. Code works the way it is... -
Indesign Pagemaker upgrade code
I just went to buy the Pagemaker upgrade to InDesign. The order process asks if I have an offer code, which would presumably make the £289 deal ... -
Can you upgrade using a previous version upgrade disk?
When upgrading to PS 7, can I use the previous version 5 upgrade media for product verification or do I need the original full version disk - which,... -
MikerRoo #2
Re: Upgrade blew up code
The best thing to do is run the code analyzer.
It will tell you all the errors with a good explanation of the fix and the
history.
The code analyzer is in the administrator in the "Debugging & Logging" section.
Once you have run through and cleared all the errors, use the "advanced
options" to turn on the warnings and run through it again.
The CF docs also list the history of changes to each tag and function.
The
[url]http://www.macromedia.com/support/documentation/en/coldfusion/releasenotes.html[/url]
also gives a good overview of the changes from version to version.
MikerRoo Guest



Reply With Quote

