Arthur Fuller
artful at rogers.com
Tue Feb 18 21:55:09 CST 2003
Try my static function solution to said problem-types. (Search for static functions and you'll find some messages on same.) Build the SQL statement or sproc invocation from a string that resolves the param(s) first then concats them into a sensible expression, then fire that. Works like a charm. You could either construct an entire SELECT statement or an EXEC mySproc parm1 parm2 parmn statement. Both work perfectly. Just keep in mind that everything must comply with SQL not with Access. I.e. single quotes not double quotes, and so on. Dates should be delimited with single quotes not pound signs, and so on. A few simple (SQL) rules and you're cool, everything will work as expected. -----Original Message----- From: dba-sqlserver-admin at databaseadvisors.com [mailto:dba-sqlserver-admin at databaseadvisors.com] On Behalf Of Julie Reardon-Taylor Sent: February 18, 2003 12:50 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer]OLEDB Connection Thanks Francisco. That makes sense. I thought that I was still using "Access" type queries and forms. Didn't realize that this was totally sql. I appreciate your answer! Julie Reardon-Taylor PRO-SOFT OF NY, INC. www.pro-soft.net _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com