>Craig Baugh

> SO, i wrote a little app to test things out on MSSQL and found that it does
> not seem to choose an index unless I prefix the table name with 'dbo.'.  Is
> there a way (setting etc) that I can get around this ?

> Thanks,
> -Orren

> My app currently relies too heavily on the findkey at this point to remove
> it....I also plan on allowing for MSSQL or Paradox to run the app.  I may go
> ahead and do what your suggesting...but my first step is working with what I
> got.

> Thanks for the advice, I will search the groups for tips.
> Any suggestions for getting around dbo/index problem though ?

> cbaugh wrote in message <86i8hq$n...@bornews.borland.com>...
> >Much better advise it to toss out your findkey and use a tquery with
> >a where clause.  Search the groups for a lot of "tips" on what to do and
> >what not to do when coming from Paradox.

> >Craig Baugh

> Thanks for the advice, I will search the groups for tips.
> Any suggestions for getting around dbo/index problem though ?

> cbaugh wrote in message <86i8hq$n...@bornews.borland.com>...
> >Much better advise it to toss out your findkey and use a tquery with
> >a where clause.  Search the groups for a lot of "tips" on what to do and
> >what not to do when coming from Paradox.

> >Craig Baugh

>Craig Baugh

>SO, i wrote a little app to test things out on MSSQL and found that it does
>not seem to choose an index unless I prefix the table name with 'dbo.'.  Is
>there a way (setting etc) that I can get around this ?

>Thanks,
>-Orren

> Thanks for all the suggestions and tips. I thought there was a setting
> (grant etc) or a way to not have to state the owner in front of the
> tablename.  I know there was using db2 with other development apps (I just
> can't remember how we did it).  I guess I will have to modify it via
> procedure or descendant.  It looks like I will have to have some sort of
> "toggle" in the code at some point to handle the SQL side, as Bradford
> suggested.

> Thanks again.

> cbaugh wrote in message <86ij0e$n...@bornews.borland.com>...
> >Please, please don't do it.  I can't stress it enough.  I've seen apps that
> ran faster
> >on paradox tables then on sql tables for the exact reason of what you are
> doing.
> >If your app can run on both sql server and paradox tables, well I imagine
> that
> >scalability will be close to 0%.  Think about what happens when you do a
> findkey
> >on paradox.  You have the table opened to that index, and you scan on it.
> Now,
> >do that on sql server, get ready to bring all of the records down.  And I'm
> sure you are
> >using ttables, the number one gotcha all time of killing sql server
> performance.   Stop
> >and scan these newsgroups before you go further. You'll thank me once you
> stop cursing
> >at me:)..

> >Craig Baugh

> HTH,

> Craig Baugh

> Orren <Orren.grush...@goldmanmarcus.com> wrote in message

> > Thanks for all the suggestions and tips. I thought there was a setting
> > (grant etc) or a way to not have to state the owner in front of the
> > tablename.  I know there was using db2 with other development apps (I
just
> > can't remember how we did it).  I guess I will have to modify it via
> > procedure or descendant.  It looks like I will have to have some sort of
> > "toggle" in the code at some point to handle the SQL side, as Bradford
> > suggested.

> > Thanks again.

> > cbaugh wrote in message <86ij0e$n...@bornews.borland.com>...
> > >Please, please don't do it.  I can't stress it enough.  I've seen apps
that
> > ran faster
> > >on paradox tables then on sql tables for the exact reason of what you
are
> > doing.
> > >If your app can run on both sql server and paradox tables, well I
imagine
> > that
> > >scalability will be close to 0%.  Think about what happens when you do
a
> > findkey
> > >on paradox.  You have the table opened to that index, and you scan on
it.
> > Now,
> > >do that on sql server, get ready to bring all of the records down.  And
I'm
> > sure you are
> > >using ttables, the number one gotcha all time of killing sql server
> > performance.   Stop
> > >and scan these newsgroups before you go further. You'll thank me once
you
> > stop cursing
> > >at me:)..

> > >Craig Baugh

> Sorry, do you mind to email me your top ten tips or to point out where I can
> find it?

> Thanks

> Peter Dam

> cbaugh <cba...@home.com> wrote in message
> news:86mtd6$poo14@bornews.borland.com...
> > I wish you luck.  I think if you will reread the newsgroups you will find
> that the
> > idea of a toggle in your code is a rather poor idea.  I earlier posted a
> list of what
> > I have found (from experience, talking to others and these newsgroups) my
> top
> > ten list for C/S development. I believe you'll find that most of these you
> will be in
> > violation of.  And if you spend enough time to truly find a way to "flip a
> switch", you
> > will find that it would have been far easier to simply have two completely
> different products
> > up front. And again, I apologize if I'm being unfriendly, I'm really
> trying to point you in the
> > direction of understanding the differences between a paradox app and a
> good c/s app.

> > HTH,

> > Craig Baugh

> > Orren <Orren.grush...@goldmanmarcus.com> wrote in message
> news:86kqqd$ond15@bornews.borland.com...
> > > I scanned through many of the C/S tips, printed them, memorized them and
> had
> > > them framed and yes I am scared.  The application won't be using both
> > > Paradox and SQL at the same time (just to be clear), it will use one or
> the
> > > other depending on user preferences etc.  So I am on a tricky tightrope
> > > here...my first priority is to get it to work with minimal changes.  Do
> some
> > > testing and then modify as needed.  And from what everyone is telling me
> is
> > > that it will be significant changes...but first baby steps.

> > > Thanks for all the suggestions and tips. I thought there was a setting
> > > (grant etc) or a way to not have to state the owner in front of the
> > > tablename.  I know there was using db2 with other development apps (I
> just
> > > can't remember how we did it).  I guess I will have to modify it via
> > > procedure or descendant.  It looks like I will have to have some sort of
> > > "toggle" in the code at some point to handle the SQL side, as Bradford
> > > suggested.

> > > Thanks again.

> > > cbaugh wrote in message <86ij0e$n...@bornews.borland.com>...
> > > >Please, please don't do it.  I can't stress it enough.  I've seen apps
> that
> > > ran faster
> > > >on paradox tables then on sql tables for the exact reason of what you
> are
> > > doing.
> > > >If your app can run on both sql server and paradox tables, well I
> imagine
> > > that
> > > >scalability will be close to 0%.  Think about what happens when you do
> a
> > > findkey
> > > >on paradox.  You have the table opened to that index, and you scan on
> it.
> > > Now,
> > > >do that on sql server, get ready to bring all of the records down.  And
> I'm
> > > sure you are
> > > >using ttables, the number one gotcha all time of killing sql server
> > > performance.   Stop
> > > >and scan these newsgroups before you go further. You'll thank me once
> you
> > > stop cursing
> > > >at me:)..

> > > >Craig Baugh

>*********
>My top eigh{*word*249}  list.
>- Use cached updates. (This allows use of the tupdatesql component).
>- Don't cache updates. Call applyupdates after each one.
>- Understand how locking works on your server.  (If you don't you will come
to regret it.)
>- If it can be done on the server, do it there.
>- Code priority.
>1. Make it a trigger.
>2. Make it a stored procedure.
>3. Make it a query called from the client.
>4. Write it at the client but figure out why you can't do it at the server

>I'm sure many will disagree (and already have) but it's good food for
thought.

>Regards,

>Craig Baugh

>Peter Dam <p...@tesco.net> wrote in message

>> Sorry, do you mind to email me your top ten tips or to point out where I
can
>> find it?

>> Thanks

>> Peter Dam

>> cbaugh <cba...@home.com> wrote in message
>> news:86mtd6$poo14@bornews.borland.com...
>> > I wish you luck.  I think if you will reread the newsgroups you will
find
>> that the
>> > idea of a toggle in your code is a rather poor idea.  I earlier posted
a
>> list of what
>> > I have found (from experience, talking to others and these newsgroups)
my
>> top
>> > ten list for C/S development. I believe you'll find that most of these
you
>> will be in
>> > violation of.  And if you spend enough time to truly find a way to
"flip a
>> switch", you
>> > will find that it would have been far easier to simply have two
completely
>> different products
>> > up front. And again, I apologize if I'm being unfriendly, I'm really
>> trying to point you in the
>> > direction of understanding the differences between a paradox app and a
>> good c/s app.

>> > HTH,

>> > Craig Baugh

>> > Orren <Orren.grush...@goldmanmarcus.com> wrote in message
>> news:86kqqd$ond15@bornews.borland.com...
>> > > I scanned through many of the C/S tips, printed them, memorized them
and
>> had
>> > > them framed and yes I am scared.  The application won't be using both
>> > > Paradox and SQL at the same time (just to be clear), it will use one
or
>> the
>> > > other depending on user preferences etc.  So I am on a tricky
tightrope
>> > > here...my first priority is to get it to work with minimal changes.
Do
>> some
>> > > testing and then modify as needed.  And from what everyone is telling
me
>> is
>> > > that it will be significant changes...but first baby steps.

>> > > Thanks for all the suggestions and tips. I thought there was a
setting
>> > > (grant etc) or a way to not have to state the owner in front of the
>> > > tablename.  I know there was using db2 with other development apps (I
>> just
>> > > can't remember how we did it).  I guess I will have to modify it via
>> > > procedure or descendant.  It looks like I will have to have some sort
of
>> > > "toggle" in the code at some point to handle the SQL side, as
Bradford
>> > > suggested.

>> > > Thanks again.

>> > > cbaugh wrote in message <86ij0e$n...@bornews.borland.com>...
>> > > >Please, please don't do it.  I can't stress it enough.  I've seen
apps
>> that
>> > > ran faster
>> > > >on paradox tables then on sql tables for the exact reason of what
you
>> are
>> > > doing.
>> > > >If your app can run on both sql server and paradox tables, well I
>> imagine
>> > > that
>> > > >scalability will be close to 0%.  Think about what happens when you
do
>> a
>> > > findkey
>> > > >on paradox.  You have the table opened to that index, and you scan
on
>> it.
>> > > Now,
>> > > >do that on sql server, get ready to bring all of the records down.
And
>> I'm
>> > > sure you are
>> > > >using ttables, the number one gotcha all time of killing sql server
>> > > performance.   Stop
>> > > >and scan these newsgroups before you go further. You'll thank me
once
>> you
>> > > stop cursing
>> > > >at me:)..

>> > > >Craig Baugh

> *********
> My top eigh{*word*249}  list.
> - Use cached updates. (This allows use of the tupdatesql component).
> - Don't cache updates. Call applyupdates after each one.
> - Understand how locking works on your server.  (If you don't you will
come to regret it.)
> - If it can be done on the server, do it there.
> - Code priority.
> 1. Make it a trigger.
> 2. Make it a stored procedure.
> 3. Make it a query called from the client.
> 4. Write it at the client but figure out why you can't do it at the server

> I'm sure many will disagree (and already have) but it's good food for
thought.

> Regards,

> Craig Baugh

> Peter Dam <p...@tesco.net> wrote in message

> > Sorry, do you mind to email me your top ten tips or to point out where I
can
> > find it?

> > Thanks

> > Peter Dam

> > cbaugh <cba...@home.com> wrote in message
> > news:86mtd6$poo14@bornews.borland.com...
> > > I wish you luck.  I think if you will reread the newsgroups you will
find
> > that the
> > > idea of a toggle in your code is a rather poor idea.  I earlier posted
a
> > list of what
> > > I have found (from experience, talking to others and these newsgroups)
my
> > top
> > > ten list for C/S development. I believe you'll find that most of these
you
> > will be in
> > > violation of.  And if you spend enough time to truly find a way to
"flip a
> > switch", you
> > > will find that it would have been far easier to simply have two
completely
> > different products
> > > up front. And again, I apologize if I'm being unfriendly, I'm really
> > trying to point you in the
> > > direction of understanding the differences between a paradox app and a
> > good c/s app.

> > > HTH,

> > > Craig Baugh

> > > Orren <Orren.grush...@goldmanmarcus.com> wrote in message
> > news:86kqqd$ond15@bornews.borland.com...
> > > > I scanned through many of the C/S tips, printed them, memorized them
and
> > had
> > > > them framed and yes I am scared.  The application won't be using
both
> > > > Paradox and SQL at the same time (just to be clear), it will use one
or
> > the
> > > > other depending on user preferences etc.  So I am on a tricky
tightrope
> > > > here...my first priority is to get it to work with minimal changes.
Do
> > some
> > > > testing and then modify as needed.  And from what everyone is
telling me
> > is
> > > > that it will be significant changes...but first baby steps.

> > > > Thanks for all the suggestions and tips. I thought there was a
setting
> > > > (grant etc) or a way to not have to state the owner in front of the
> > > > tablename.  I know there was using db2 with other development apps
(I
> > just
> > > > can't remember how we did it).  I guess I will have to modify it via
> > > > procedure or descendant.  It looks like I will have to have some
sort of
> > > > "toggle" in the code at some point to handle the SQL side, as
Bradford
> > > > suggested.

> > > > Thanks again.

> > > > cbaugh wrote in message <86ij0e$n...@bornews.borland.com>...
> > > > >Please, please don't do it.  I can't stress it enough.  I've seen
apps
> > that
> > > > ran faster
> > > > >on paradox tables then on sql tables for the exact reason of what
you
> > are
> > > > doing.
> > > > >If your app can run on both sql server and paradox tables, well I
> > imagine
> > > > that
> > > > >scalability will be close to 0%.  Think about what happens when you
do
> > a
> > > > findkey
> > > > >on paradox.  You have the table opened to that index, and you scan
on
> > it.
> > > > Now,
> > > > >do that on sql server, get ready to bring all of the records down.
And
> > I'm
> > > > sure you are
> > > > >using ttables, the number one gotcha all time of killing sql server
> > > > performance.   Stop
> > > > >and scan these newsgroups before you go further. You'll thank me
once
> > you
> > > > stop cursing
> > > > >at me:)..

> > > > >Craig Baugh