Does access 2003 support batchupdates ?

[Malcolm Cook]

I read that MS made a mistake in Access 2002 - it does not support batch
update processing but released lots of documentation with the product
stating that it does.

Does anyone know if this has been addressed in 2003?

I've looked on line at microsoft but can't find an answer.

Here is the admission from MS:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnacc2k2/html/odc_csbatchtrans.asp

Summary: Microsoft Access 2002 does not provide native support for batch
updates and transactions. In addition, a number of previously-documented
elements are not implemented.

Any other pointers on fixes in 2003 much welcomed.

Please excuse cross-posting to news://microsoft.public.data.ado - I
should've posted here instead....

Thanks

Malcolm E. Cook
Stowers Institute for Medical Research

 

[Lyle Fairfield]

I read that MS made a mistake in Access 2002 - it does not support batch
update processing but released lots of documentation with the product
stating that it does.

Does anyone know if this has been addressed in 2003?

I've looked on line at microsoft but can't find an answer.

Here is the admission from MS:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnacc2k2
/html/odc_csbatchtrans.asp

Summary: Microsoft Access 2002 does not provide native support for batch
updates and transactions. In addition, a number of previously-documented
elements are not implemented.

Any other pointers on fixes in 2003 much welcomed.

Please excuse cross-posting to news://microsoft.public.data.ado - I
should've posted here instead....

Thanks

Malcolm E. Cook
Stowers Institute for Medical Research

Well, nobody does good work these days. Johnson & Johnson has admitted that
Tylenol does not do brain surgery.

 

[SFAxess]

Microsoft has a white paper (301987) which discusses the
inability of the form's recordset property to accommodate
batch updates. It recommends some possible work arounds,
but offers no definitive solution. It may help.
http://support.microsoft.com/default.aspx?scid=kb;en-
us;301987

-----Original Message-----
I read that MS made a mistake in Access 2002 - it does not support batch
update processing but released lots of documentation with the product
stating that it does.

Does anyone know if this has been addressed in 2003?

I've looked on line at microsoft but can't find an answer.

Here is the admission from MS:

http://msdn.microsoft.com/library/default.asp? url=/library/en-us/dnacc2k2/html/odc_csbatchtrans.asp

Summary: Microsoft Access 2002 does not provide native support for batch
updates and transactions. In addition, a number of previously-documented
elements are not implemented.

Any other pointers on fixes in 2003 much welcomed.

Please excuse cross-posting to

news://microsoft.public.data.ado - I

 

[Malcolm Cook]

THanks for pointing out that white paper.

However, in reading it, I am dismayed that the only offered 'workaround' is:
"One approach you can use to obtain this functionality is to unbind the form
completely, and then use ADO code to populate unbound controls on the form
with data from the recordset. This gives you the most control over your
application. However, it requires the most work because you have to manage
the navigation and updating of your recordset completely."

If you know of any similar white papers discussing internals of 2003 I'd
like to hear of them...

Thanks again,

Malcolm

 

[Vadim Rapp]

Hello Malcolm:
You wrote in conference microsoft.public.access.adp.sqlserver on Tue, 13
Apr 2004 14:13:06 -0500:

MC> I read that MS made a mistake in Access 2002 - it does not support
MC> batch update processing but released lots of documentation with the
MC> product stating that it does.

MC> Does anyone know if this has been addressed in 2003?

Looking at the set of those keywords, I can bet $100 that they won't be
implemented ever. The current trend in the database technology is not
towards transaction-oriented processing, but exactly in the opposite direction:
quickly grab the data; disconnect; work with the data offline; then upload
the data back to the server. The reason for this wisdom, of course, is
webpage-oriented stateless processing.

What's interesting, is that in fact I have found an undocumented way to make
Access ADP to work with server-based cursors, thus with transaction support,
commits and rollbacks. It appears that the work in that direction was
started, but then decision was made that it's not what users would be
interested in. So it was shut down.

If you read database-oriented literature these days, you won't easily find
words like transactions, locks, escalations, commits, etc. These are
artifacts of the past.

Vadim