The following works fine in Access 2003. However, in SQL it fails with "Invalid Column Name".
In Access you can create a new column, in our case "Margin" and immediately use it in futher calculations. I am a total rookie in TSQL so would like some ideas on the best way to solve this type of...
We are changing the data source to a different, although very similar, stored procedure. This, of cource, breaks the CR. Is there any easy way to point the fields, groups etc. to the new procedure? (CR 9)
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.