Re: Converting from ADP to MDB/ODBC linked tables

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,

Wasn't meant to be a rebuttal, just some advice. I'd hate to see someone
abandon Access when it's still perfectly usable.

Don't get me wrong, I don't dislike ADP's, I've done some serious
applications using them. Bugginess is, I suppose, a relative concept. A
search of Google Groups will reveal lots of discussions about the many
problems with ADP's and the relative merits (and demerits) of ADP's and ODBC
linked tables. Just ignore anything from that idiot Kempf.


"Reese Watt" <reese@xxxxxxxxxxxxxxxxx> wrote in message
news:%23t4nUC70HHA.4184@xxxxxxxxxxxxxxxxxxxxxxx
Baz,

Ok. Thanks for the rebuttal. Maybe I overreacted. I'll give it serious
consideration if I do actually come to the point where I need to convert.

I don't consider ADP's to be buggy, by the way. For me, it's been great.

Reese







"Baz" <bazz@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:46aedf70$0$31725$db0fefd9@xxxxxxxxxxxxxxxxx
It shouldn't be. ODBC linked tables worked fine for years before ADP's
and
they still do (and it's a lot less buggy than ADP's). I have used them
to
successfully build huge multi-user systems with hundreds of server
objects
and hundreds of Access objects. There is always the option of using
passthrough queries for the (quite rare) occasions when you encounter
some
limitation of ODBC linked tables; or, you can build a server view and
link
to that.

If you abandon this approach without seriously trying it you are really
shooting yourself in the foot: either you battle on with ADP's and just
pray
that MS doesn't pull the rug out from under you, or you change to VB.Net
or
Delphi and increase your development costs by several multiples at
least..

"Reese Watt" <reese@xxxxxxxxxxxxxxxxx> wrote in message
news:efcQZLu0HHA.3848@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for the responses.

I don't like what I read about the limits of ODBC queries. I think
that
would be a deal-breaker for me as far as converting to and MDB/ODBC
combination.

"Reese Watt" <reese@xxxxxxxxxxxxxxxxx> wrote in message
news:u9gNzAG0HHA.1100@xxxxxxxxxxxxxxxxxxxxxxx
Hello all,

Does anybody have any experience converting an ADP file to an MDB
file
using linked SQL tables via ODBC?
(By the way, is linking via ODBC the same as using a pass-through
query?)

For example, assume I took these steps:
1) Create new mdb file
2) Import Form1 into the newly created mdb file from my existing adp
file,
which was bound to View1 (in SQL server)
3) Link to View1 via ODBC
4) Bind the Form1 in the new mdb file to the linked View1

Would my Form1 need to be modified to work under the new structure?
How difficult would it be to modify it?

Thanks,

Reese









.

Quantcast