Well, I thought I had figured it out when I posted in my previous post 
regarding this. However the issue reared it's ugly head once again and I was 
back to square one. Anyway, here's what I have done. I will be uploading to 
my site a zipped file so you can download and check it out. The file will 
contain the cfm templates, associated cfc's, a SQL table script, and a 
stored procedure script so you can check it out yourself. Here's the list of 
folders and files:
*Test Folder*
* - cfceoc subfolder*
- eocsessvar.cfm
* - inceoc subfolder*
- eoc1fltslct.cfm
- eoc2school.cfm
*- Script subfolder*
- tester.sql (table creation script)
- spInsertEOCTester.sql (stored procedure script)
- Application.cfc
- formdump.cfm
- sashstyle.css
- soseoc.cfm
- sosinsert.cfm
- textCounter.js
 Those are all the files. 
Here's the link: http://www.linguiphile.net/test.zip
Here's a quick explanation of what's used:
*Appserver:* Coldfusion MX 7 (Dev Edition on Windows XP, Standard on Windows 
2000)
*Database:* MSSQL 2000
To create the table and the associated stored procedure you will need to 
open up either Query Analyzer or Enterprise Manager and run the above 
scripts in your database of choice.
 The insert stored procedure works fine and inserts data without any issues 
(accomplished in Query Analyzer). The cfm templates work fine collecting 
variables and kicking them out into their respective SESSION variable 
containers. The choke point happens when the form goes to submit the 
variables and pass them to the cfprocparam in the cfstoredproc. Here's the 
error that I get:
*Invalid data SESSION.tester.ClsFltID for CFSQLTYPE CF_SQL_NUMERIC. 

The error occurred in C:\Inetpub\wwwroot\SOCEVAL\test\sosinsert.cfm: line 13

11 : <cfprocparam type="in" cfsqltype="cf_sql_numeric" dbvarname="ClsFltID" 
value="SESSION.tester.ClsFltID">
12 : <cfprocparam type="in" cfsqltype="cf_sql_integer" 
dbvarname="MissionRat" value="SESSION.tester.MissionRat">
13 : <cfprocparam type="in" cfsqltype="cf_sql_varchar" maxlength="2000" 
dbvarname="MissionCom" value="SESSION.tester.MissionCom">
14 : </cfstoredproc>
15 :*
  And of course, in true CF glib fashion, the first line is "where" the 
error occurs yet the last line of the cfprocparams is highlighted. So that 
is where my choke point is. Just for the measure. I prefer to use Stored 
Procedures and that is what I am trying to figure out to kill this choke 
point. Thanks for any help on this, as my head has suffered much bruising 
from the wall and my muse, the internet (oh false god that it is, alas, I 
still worship it), has failed me this time.
Tom


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Find out how CFTicket can increase your company's customer support 
efficiency by 100%
http://www.houseoffusion.com/banners/view.cfm?bannerid=49

Message: http://www.houseoffusion.com/lists.cfm/link=i:6:2374
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/6
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:6
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.6
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to