Flaws in Access (resource)

[Allen Browne]

To help you avoid some of the more common and long-standing bugs in Access,
the page:
http://allenbrowne.com/tips.html
contains a new section entitled, "Flaws in Access".

The section currently identifies 9 problem areas, with others to be added.
It includes a sample Access 2000 database to demonstrate several of the
flaws. If you have been working with Access, you will be aware of some of
them. Our aim is to prevent you grief by pin-pointing the rocks under the
surface.

Best wishes for your Accessing in 2004.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

[Wayne Morgan]

Nice list Allen, thank you.

--
Wayne Morgan
Microsoft Access MVP
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:3f******** **************@ freenews.iinet. net.au...

To help you avoid some of the more common and long-standing bugs in Access, the page:
http://allenbrowne.com/tips.html
contains a new section entitled, "Flaws in Access".

[Steve Jorgensen]

Thanks Allen,

I would add another issue to the "Writing the wrong record". Besides the
"Bookmark bug", there is a bug that exists in Access 2000 and 2002 that does
not seem to have been fixed in any service pack, and the workaround shown on
Microsoft's support page does not work.

The problem is when you have editable controls in the header and/or footer of
a form. If you edit one of these controls, then click on another row in the
continuous section, the new record's data is not displayed in the
header/footer control. Furthermore, if you type anything into that control,
it writes to the other record.

The only work-around I've ever gotten to work is to execute the .Requery
method on every control that could be effected from the form's Current event
handler.

On Tue, 30 Dec 2003 19:41:17 +0800, "Allen Browne"
<Al*********@Se eSig.Invalid> wrote:

To help you avoid some of the more common and long-standing bugs in Access,
the page:
http://allenbrowne.com/tips.html
contains a new section entitled, "Flaws in Access".

The section currently identifies 9 problem areas, with others to be added.
It includes a sample Access 2000 database to demonstrate several of the
flaws. If you have been working with Access, you will be aware of some of
them. Our aim is to prevent you grief by pin-pointing the rocks under the
surface.

Best wishes for your Accessing in 2004.

[Arno R]

Allen,
Very useful info, thanks
BTW: Something 'buggy' with your dates?
It is still 2003 here ... <grin>

Flaws in MS Access
Provided by Allen Browne, January 2004

Arno R
"Allen Browne" <Al*********@Se eSig.Invalid> schreef in bericht
news:3f******** **************@ freenews.iinet. net.au... To help you avoid some of the more common and long-standing bugs in Access,
the page:
http://allenbrowne.com/tips.html
contains a new section entitled, "Flaws in Access".

The section currently identifies 9 problem areas, with others to be added.
It includes a sample Access 2000 database to demonstrate several of the
flaws. If you have been working with Access, you will be aware of some of
them. Our aim is to prevent you grief by pin-pointing the rocks under the
surface.

Best wishes for your Accessing in 2004.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

[Larry Linson]

Perhaps it _is_ already 2004 on the clock/calendar in Australia?
"Arno R" <ar************ ****@tiscali.nl > wrote in message
news:3f******** **************@ dreader2.news.t iscali.nl...

Allen,
Very useful info, thanks
BTW: Something 'buggy' with your dates?
It is still 2003 here ... <grin>

Flaws in MS Access
Provided by Allen Browne, January 2004
Arno R
"Allen Browne" <Al*********@Se eSig.Invalid> schreef in bericht
news:3f******** **************@ freenews.iinet. net.au...

To help you avoid some of the more common and long-standing bugs in

Access, the page:
http://allenbrowne.com/tips.html
contains a new section entitled, "Flaws in Access".

The section currently identifies 9 problem areas, with others to be added. It includes a sample Access 2000 database to demonstrate several of the
flaws. If you have been working with Access, you will be aware of some of them. Our aim is to prevent you grief by pin-pointing the rocks under the surface.

Best wishes for your Accessing in 2004.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

[Arno R]

> Perhaps it _is_ already 2004 on the clock/calendar in Australia?

No, not yet on my (world) clock/calendar ...
In Sidney it's about 10 AM now (12-31-2003)

Arno R

[Allen Browne]

Hi Steve.

Yes, I had that issue in Access 2000, but could not repro. quickly in A2003.
Have you seen it in the current version?

It was really a display issue where Access displayed the old data for a memo
field in the form footer section. As soon as you clicked in the field to
edit it, the text box was updated, so there was no danger of overwriting it.

I'm interested if you can repro in A2003.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Steve Jorgensen" <no****@nospam. nospam> wrote in message
news:8t******** *************** *********@4ax.c om...

Thanks Allen,

I would add another issue to the "Writing the wrong record". Besides the
"Bookmark bug", there is a bug that exists in Access 2000 and 2002 that does not seem to have been fixed in any service pack, and the workaround shown on Microsoft's support page does not work.

The problem is when you have editable controls in the header and/or footer of a form. If you edit one of these controls, then click on another row in the continuous section, the new record's data is not displayed in the
header/footer control. Furthermore, if you type anything into that control, it writes to the other record.

The only work-around I've ever gotten to work is to execute the .Requery
method on every control that could be effected from the form's Current event handler.

On Tue, 30 Dec 2003 19:41:17 +0800, "Allen Browne"
<Al*********@Se eSig.Invalid> wrote:

To help you avoid some of the more common and long-standing bugs in Access,the page:
http://allenbrowne.com/tips.html
contains a new section entitled, "Flaws in Access".

The section currently identifies 9 problem areas, with others to be added.It includes a sample Access 2000 database to demonstrate several of the
flaws. If you have been working with Access, you will be aware of some of
them. Our aim is to prevent you grief by pin-pointing the rocks under the
surface.

Best wishes for your Accessing in 2004.

[Allen Browne]

You're right: I did not anticipate actually making these pages live until
2004, but managed to output them yesterday.

Good catch.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Arno R" <ar************ ****@tiscali.nl > wrote in message
news:3f******** **************@ dreader2.news.t iscali.nl...

Allen,
Very useful info, thanks
BTW: Something 'buggy' with your dates?
It is still 2003 here ... <grin>

Flaws in MS Access
Provided by Allen Browne, January 2004
Arno R
"Allen Browne" <Al*********@Se eSig.Invalid> schreef in bericht
news:3f******** **************@ freenews.iinet. net.au...

To help you avoid some of the more common and long-standing bugs in

Access, the page:
http://allenbrowne.com/tips.html
contains a new section entitled, "Flaws in Access".

The section currently identifies 9 problem areas, with others to be added. It includes a sample Access 2000 database to demonstrate several of the
flaws. If you have been working with Access, you will be aware of some of them. Our aim is to prevent you grief by pin-pointing the rocks under the surface.

Best wishes for your Accessing in 2004.

[Steve Jorgensen]

On Wed, 31 Dec 2003 09:13:27 +0800, "Allen Browne"
<Al*********@Se eSig.Invalid> wrote:

Hi Steve.

Yes, I had that issue in Access 2000, but could not repro. quickly in A2003.
Have you seen it in the current version?
No, but it is definitely still a problem in A2002.

It was really a display issue where Access displayed the old data for a memo
field in the form footer section. As soon as you clicked in the field to
edit it, the text box was updated, so there was no danger of overwriting it.
I've had the problem in both 2000 and 2002 where it actually writes to the
wrong record, and is not just a display problem.

I'm interested if you can repro in A2003.

Me too, but I don't have it. I could try it with the beta, but the results
won't be definitive.

[Michael \(michka\) Kaplan [MS]]

Nice list, though one thing:

The "currency format" issue is NOT a bug. It is entirely by design and it
MUST be this way. An application that turned 1000 US Dollars into 1000
Italian Lira is an app that was produced by a company that is going to go
out of business.... think about.

This design was championed by the International Program Manager back in
Access 2.0, and she was entirely right. I would highly recommend that this
item be taken off of the list of bugs and put in a more appropriate list of
"issues to not trip over" as the current design is correct an any other
design is an incredibly lame an ill-conceived notion.
--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies

This posting is provided "AS IS" with
no warranties, and confers no rights.
"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:3f******** **************@ freenews.iinet. net.au...

To help you avoid some of the more common and long-standing bugs in Access, the page:
http://allenbrowne.com/tips.html
contains a new section entitled, "Flaws in Access".

The section currently identifies 9 problem areas, with others to be added.
It includes a sample Access 2000 database to demonstrate several of the
flaws. If you have been working with Access, you will be aware of some of
them. Our aim is to prevent you grief by pin-pointing the rocks under the
surface.

Best wishes for your Accessing in 2004.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.