Ok.. grrr... here's an interesting question for the SQL DBA Guru Gods (and Goddesses). The client is on a shared host. Dedicated web server, but shared SQL server - we only have one DB to play with. Can I create an ODBC source for the client storage only, while still using OLEDB for the rest of the site, or will this cause problems with the system tables, etc? I know you should never define multiple ODBC or OLEDB sources for accessing/manipulating the same tables.
-----Original Message----- From: Admin [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 05, 2002 11:30 AM To: CF-Talk Subject: Re: Odd OLEDB Error I never got that working using oledb. I think you will have to stick with odbc for CVS. It seems to be a Cold Fusion 'feature' and has been like that since Cf 4.0 ----- Original Message ----- From: "Jeff Beer" <[EMAIL PROTECTED]> > Hrmm.. I found the problem. It wasn't that query - it was CF trying to use > an OLEDB datasource for Client variable storage. I temporarily switched it > to the system registry (ack!) and the problem went away. ______________________________________________________________________ Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
