Complain at Access2003

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Totoro - 21 Jan 2005 16:31 GMT

Access2003 is hard to use compaire 97 at followings,
1) In form and report, border line is not printed properly
2) Response is so slow in form/report design change
3) Need copy/past (mouse right click) function in Expression Builder
4) Newly saved objects are not listed in alphabetic order in Expression
Builder
5) In macro condition, =Null, <>Null are not changed to "is Null" or "Is not
Null"
6) Can not change/save any object, when some one opens any other object.
Very inconvenience to change.
7) Outlook shows "Virus Warning" when Access try to send email by
SendObject. email is used as notification system of data entry and machine
performance. When "No" is clicked, we can not monitor.

Reply to this Message

Rick Brandt - 21 Jan 2005 18:18 GMT

> Access2003 is hard to use compaire 97 at followings,
> 1) In form and report, border line is not printed properly
[quoted text clipped - 9 lines]
> SendObject. email is used as notification system of data entry and
> machine performance. When "No" is clicked, we can not monitor.

Wadda ya gonna do? Many feel that Access peaked at 97, but there's nothing
you can do except NOT upgrade.

By the way, number 7 has to do with the version of Outlook and nothing to do
with the version of Access.

Signature

I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Reply to this Message

John Vinson - 21 Jan 2005 18:22 GMT

>Access2003 is hard to use compaire 97 at followings,
>1) In form and report, border line is not printed properly

Haven't seen that but it's quite likely a real bug.

>2) Response is so slow in form/report design change

Turn off Name Autocorrect; it's slow and it's very buggy

>3) Need copy/past (mouse right click) function in Expression Builder

Ctrl-C to copy, Ctrl-V to paste - but yes, the mouse would be nice.

>4) Newly saved objects are not listed in alphabetic order in Expression
>Builder

AGREED! A *real* annoyance.

>5) In macro condition, =Null, <>Null are not changed to "is Null" or "Is not
>Null"

Is Null and Is Not Null is the correct syntax. Null means "this value
is undefined, unknown" - as a result the value of <anything> = Null is
neither true nor false, it is NULL. Access is changing your erroneous
syntax to the only correct syntax which will work.

>6) Can not change/save any object, when some one opens any other object.
>Very inconvenience to change.

ummmm... not in my experience.

>7) Outlook shows "Virus Warning" when Access try to send email by
>SendObject. email is used as notification system of data entry and machine
>performance. When "No" is clicked, we can not monitor.

Haven't worked with this myself.

John W. Vinson[MVP]

Reply to this Message

Allen Browne - 22 Jan 2005 08:06 GMT

Interesting list. Answers embedded, to add to the good replies you already
received.

There are some additional issues you may need to be aware of in this
article:
Converting from Access 97
at:
http://members.iinet.net.au/~allenbrowne/ser-48.html

Signature

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.

> Access2003 is hard to use compaire 97 at followings,
> 1) In form and report, border line is not printed properly

Could be a printer driver issue.

> 2) Response is so slow in form/report design change

This is largely fixable. See:
Access Performance FAQ
by Tony Toews at:
http://www.granite.ab.ca/access/performancefaq.htm

> 6) Can not change/save any object, when some one opens any other
> object. Very inconvenience to change.

It is inconvenient, but I suspect that this was a source of corruption in
A97 anyway. Ultimately, it is possible to configure and use A2003 in such as
way that it is *more* stable than A97 for development. Personally, I don't
mind losing this flexibility if it corrupts less often.

Reply to this Message