Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
elwoos
Master Smack Fu Yak Hacker
2052 Posts |
 Posted - 2003-02-20 : 12:09:43
|
| HiI am using SQl server 7 with an Access 97 client. I wrote a view with a whole series of views based on it. In the main view I used aliases with a full stop in them, tested it on the server and all seemed fine. However, when I came to link to Access I got an error message which I eventually traced to the use of full stops in the alias names. In the main query I have now replaced all the full stops with underscores. What I want to know is this:- Is there some fairly speedy way I can change all the dependent queries so that they now use an underscore instead of a full stop. If I script the queries concerned and use a find an replace will this work or is there a better way? Will I have to do them all by hand?thanks in advancesteve |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-02-20 : 12:58:43
|
| Yeah, scripting them out, replacing the characters, then running the scripts to recreate them should work without too much hassle, as long as it doesn't require dropping tables.However, it would make life a lot easier if you only used alphanumeric characters in your column/table/view names. No spaces, no underscores, no stops, nada. You can always capitalize the first letter of a word boundary, like CustomerFirstName. If someone else could not figure out a name with that kind of convention it's highly unlikely that adding special characters would help. If you absolutely had to, you could use underscores safely, but ultimately the only thing that special characters do is make the names longer and bring up subtle naming problems when transferring to another system. |
 |
|
|
|
|
|
|
|
To script or not to script