Larry Linson wrote:
"lylefair" wrote
> Remove the button (and any code associated with it).
> Let Access do the form/record save management.
> After that:
> Study Access for 15 years.
> Develop for 15 years.
> If you come up with a better way than the Access way, contact MS and
> suggest that they implement this better way in the next version.
> Then:
> Wait for the next version.
> After that:
> Let Access do the form/record save management.
I think, perhaps, you underestimate the experience required to come up with
improvements on Access. There certainly are people within Microsoft who
presumably have adequate background to, are in a position to, and try to,
come up with "better ways", and, arguably, they can't come up with many
_real_ improvements. :-)
Larry Linson
Microsoft Access MVP
I'll take this further off topic. Access is tough to beat but not
because some people at MS can't improve it much (I saw the smiley). I
don't doubt that there are people at Microsoft who can make an
application's code nearly flawless. It's just that they won't let
those people near the software :-). You'd almost think the future
direction of Access was the same way. MS was able to integrate the
internet into the OS. They weren't as successful at integrating the
internet into Access - yet. It would indeed take a lot of
sophistication to replace Access. I hope that MS will get internet
integration with Access right and not have to look over their shoulder
for newcomers. I think Access as a RAD tool for internet development
would be unbeatable. Once the application is sketched out using Access
a decision can be made whether or not to flesh it out using .NET
(ignoring things like optimization of SQL Server for now), hopefully
after applying new painless conversion tools. I want to be able to
create an internet/intranet application almost as easily as I can
create an mdb. Is that asking too much?
James A. Fortune