Lisa,<BR><BR>I typically get this error if I'm trying to - say - use a string instead of an integer in a parameter for a sql server stored procedure or something. I get the error on the .asp page as I try to append this illegal value.<BR><BR>What is the context of the area of code that is generating the error? :)<BR><BR>~ Jen
Hi Jen...just read your post.<BR>I get the error when I try to call a stored procedure.<BR>The weird thing as I posted above this morning is this code works fine on our live server but on our development server I get this error. The code is the exact same???
Hi Lisa,<BR><BR>I would first check to see that both dev and prod servers are talking to the same database. If they are not your ddl's might be different. If the db's are the same then check the operating systems. If your Dev server is running NT 4 and your production is on Windows 2000 the solution to your problem could lie there. Check out msdn to see what they say about 'issues' related to migrating. I seem to remember something about datatype problems when we moved to Win2k. If that's not the problem then check to see that your db's are running on the same drivers.<BR><BR>Good Luck and be sure to let us know what your solution is!!<BR><BR>Rich<BR><BR>