Access 2000 project connections

[VivN]

I want to use Access 2000 as a front end to a SQL server database and
have decided that Access 2K project is the way to go. This mean that I
can largely reuse my existing forms and reports (with a bit of
tweaking).

I will need a number of stored procedures to call when processing data
and have some example code using ADO to call these. This code involves
creating a connection object each time, then detroying it when
finished.
My question is this
Is it better to use the connection object that is created when the
user logs on instead of creating a new one each time? If this is so,
how do I reference it?

Also, if anyone has any useful tips that they wish they knew when they
started I would be very grateful.

Thanks in advance, Viv

[Lyle Fairfield]

vi*****************@whnt.nhs.uk (VivN) wrote in
news:c9**************************@posting.google.c om:

I want to use Access 2000 as a front end to a SQL server database and
have decided that Access 2K project is the way to go. This mean that I
can largely reuse my existing forms and reports (with a bit of
tweaking).

I will need a number of stored procedures to call when processing data
and have some example code using ADO to call these. This code involves
creating a connection object each time, then detroying it when
finished.
My question is this
Is it better to use the connection object that is created when the
user logs on instead of creating a new one each time? If this is so,
how do I reference it?

Also, if anyone has any useful tips that they wish they knew when they
started I would be very grateful.

Thanks in advance, Viv

CurrentProject.Connection is reliable, but many times slower than a roll-
your-own OLEDB-ADO connection. Whether that slowness will be noticeable
depends upon the complexity of your procedures and the frequency of their
execution.

Useful tips? Is "DON'T" useful? I used to be one of ADPs' greatest fans.
Now I would not embark on any major ADP application unless there was some
special incentive (special incentive=boatloads of cash). Why?
I think that ADPs cannot be both secure and efficient (concurrently);
ADPs seems to have been developed as many strands. These strands are not
consistent. Often it's very difficult to identify the strand with which one
is working; after one identifies a strand discovering its properties may
range in difficulty from challenging to impossible, AND worst of all,
tomorrow the ADP may use a different strand to accomplish exactly the same
task.
ADPs are extremely sensitive to the state of MDAC and Access. Haven't got
the LATEST of the LATEST? Too bad; your application dies! Have a nice day!
Maintaining Access 2000, 2002, 2003, 9? different service packs, Windows XP
SP 2, and the various manifestations of MDAC (did I mention JET and its
updates? they don't come as part of MDAC any more ... don't need JET with
ADPS? hmmmm??? ... for sure? ... doesn't Access use some JET internally for
everything?) across 70 sites, 200 desktops and 100 notebooks? Can this be
done?
Arghhhhhhhhhhhhhhhhhhhhhhh!
It's insane that we let MS continue from one failure to another to another;
shouldn't our software just WORK for a few years. Didn't we pay for that?
*** seems to have become a rant ... sorry ***
--
Lyle
--
From ADO28.chm