I give up, ADP's just don't work

[Guest]

Well after fiddling with it for two weeks and following every suggestion I've
seen here (many of them DID help BTW) I give up - ADP's open and pretend to
run, but will randomly cause Access to crash out -- no, not an error or VB
problem, crash right out to the desktop. It will work fine on one machine,
but the machine beside it dies, there appears to be no pattern other than the
version of Access installed.

I'm trying to re-implement the project as a linked-table Access MDB instead.
Yay!

Maury

 

[James Goodman]

I have had great success using ADP's & find they run very reliably. You get
no help with SQL generated error messages (a standard ado error if memory
serves), so I debug all of my SQL components from Query Analyzer.

 

[Guest]

I have had great success using ADP's & find they run very reliably. You get
no help with SQL generated error messages (a standard ado error if memory
serves), so I debug all of my SQL components from Query Analyzer.

As always, YMMV. I'm not making this up, this is happening all the time
here. The project is saved as a 2000 ADP, but was created on 2003. It works
on 2003 boxes, but fails at different times and symptoms on 2000, 2000SP1,
2000SP3, 2002 and 2002SP3, the versions I have on the network. So Bob's box
#1 with 2002SP3 works fine, the one beside it randomly crashes.

Maury

 

[Sylvain Lafontaine]

If you are taking the precaution of using Views for your SELECTs on joined
tables, you can achieve nearly the same performance as ADP in many cases.

For updating, you will trouble with views if you don't take the following
simple precaution:

http://support.microsoft.com/kb/q209123/

S. L.

 

[Guest]

If you are taking the precaution of using Views for your SELECTs on joined
tables, you can achieve nearly the same performance as ADP in many cases.

I hadn't considerd this approach, simply because it seems unnessesary. But
if it fixes the problem it's certainly worth doing -- as well, it may offer
some performance benefits.

But I don't see how it avoids a recordset lookup unless I make one "super
view" with all sorts of joins in it. This does seem rather suspect.

I just wish recordset's worked. Why shouldn't they?

Maury