I totally agree about the recorset thing; sounds EXACTLY the way i
remembered it.
I personally haven't ever had to use the form_error event.. never
really had a reason to i guess..
Lemme give you a f'rinstance:
You have a bound form. On the bound form, you have a combo box, which get's
it's row source from a related table. Your user opens the form, starts a
new record, and chooses a value in the combo box. Before he/she saves the
record, some other user deletes the record from the related table (or
changes it's primary key). Result: foreign key constraint violation. How
you gonna trap that? How you gonna give your user a sensible error message
in English? (and don't tell me that you will simply validate the field in
the BeforeUpdate event: there will still remain a "gap" where the related
record can be deleted before the INSERT hits the server).
i just do simple bound ADPs and I _LOVE_ them.
And I want to know why people are so anti-adp.
I am so friggin sick and tired of having to copy queries between
frontends.
I dont agree with your BS about ADO. ADO is much better than DAO.. for
uh.. ANYTHING and anything that tells you otherwise is stuck in 1996.
DAO was a 4-year object model and ADO has been like a 7-year object
model.
Anyone using DAO after the release of Office 2000 should be SHOT.
There are better ways to do things.
DAO addnew, update, edit, delete
THESE ARE ALL A WASTE OF TIME. Editing recordsets is for sissys that
dont know how to write SQL.
Given that you have already made a bit of a fool of yourself elsewhere on
this thread, I don't think you are in a strong position to be accusing other
people of "BS". Also, I must ask, are you incapable of carrying on a
discussion without resorting to juvenile abuse?
Incidentally, and FWIW, if you had read my comments properly, all I said
about ADO in itself was that it works very well. My criticism was for the
fact that Microsoft has made ADO obsolete, and yet we are more-or-less
compelled to use it in ADP's. That isn't a criticism of ADO, it's a
criticism of Microsoft. You may be happy to keep going down the blind alley
of Microsoft's most redundant data access technology, but personally I'd
rather be using something that has a future.
I just dont understand what in the heck you're talking about.. MDB/ODBC
outweigh ADP?? yeah.. maybe on the suck-meter
I'm not going to rehearse all the arguments again, it's been done so often
before. Go and find the discussions on Google - if your mind is not totally
closed, that is. BTW, make sure you pick up all those toys and put them
away first.
I mean-- what in the heck are you talking about.
MDB / ODBC makes things about 100 times more complex; and it's utterly
unusable in my book.
My installed base of happy users proves otherwise.
I have MDB/ODBC in my bag--- for DEVELOPMENT; not for production use.
Fine, suit yourself.
I love Access-- i wouldn't be the 'Sr SQL Developer' that I am today if
it weren't for MDB. And I claim that there are hundreds, thousands,
millions of people that can use ADP in order to learn more about SQL
Server.
Ohhh, a 'Sr SQL Developer'. Well, excuuuuse me! Although I must say that
your general attitude and demeanour mark you out as very much a "Junior".
And I think that it's the best data entry platform in the world.
I mean--- aren't you TIRED of changing sql passthroughs? Aren't you
tired of half of your code building SQL statements in order to update
Sql passthroughs?
The parameters and sprocs concept is much more powerful in ADP than
anything available in MDB. Do you know how to bind a form to a sproc?
Where if you have a parameter in a form; you can bind that to a form
field??
Just like you can in MDB?
Sorry, I feel no need to get into a pissing contest with you.
It's the most beautiful thing in the world kid.
You want to get out a bit more. Go back to the beginning of this thread and
read it again, and then ask yourself if you are in any position to patronise
people.
aren't you TIRED of having these circa-1996 errors?
MDB are _SHARP_ for a lot of things. But Microsofts' refusal to fix
bugs makes them unusable.
New versions of Jet and DAO coming along with Office 12. It's very much
back in development (unlike ADO).
Have you closed your mind so much that you are blind to the fact that ADP's
also suffer from bugs (some of which are unfixed since A2000)?
I just think that it's horse shit when people talk smack about ADP
because I dont think that most of these people know WTF they're doing.
-Aaron
I just think it's very sad when people attach themselves to just one
technology, blind themselves to everything else and start throwing their
toys around when anyone dares point out that there are two sides to
everything.
