The quote setting is set at the database level. You must not mix them.
As you convert code, you can test using ' on a copy of the ddb and
rewrite to " just before installing, while your 6.5 users are still
connected. Then, keeping your test code aside, you can switch to ' when
all the db functions are converted. Many and Single are subject to the
same restrictions.
On the other hand, you could follow my example, and stay with " if the
db is already running that way.
SQL Police, stop reading NOW! There is one severe disadvantage to single
quotes. What the heck do you do with a name like O'Brien? Although
standards are standards, the hoops we jump through to get around this
problem disappear with the double quote as standard. No standard is
perfect in every instance.
Heffelfinger, Duane wrote:
We have a large database here that still has some 6.5 dos users
connected to it. I know, not good. But my question is; Can my dos
users continue using their code with QUOTES set as ", while I write my
new code using the QUOTES set as ' on the same database? Or is the
QUOTES setting stored with the database and I can't mix? This would go
the same for the MANY, SINGLE standards too.
