YOu will have to recreate them in SQL server as user-defined functions. Be aware that UDfs are performance hogs and it might be better to actually put the code in the queries than run a UDF.
Not sure what you mean by "put the code in the queries" Every line of code from a function will reside in the SQL statement? If that's so, how does that work and where would I put it - in the WHERE cluase?
You have to translate the VBA statements to comparable T-SQL statements, but that's the way it works. If they're in the WHERE clause in Access, they need to be in the WHERE clause in SQL.
SQLSister, I've had pretty good luck with some nasty UDFs. Do you have any links to discussion about UDF performance?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.