Need to upgrade - 2002 or 2003?

[Stephan Golux]

It seems I have run afoul of an unfixable and acknowledged bug in my
beloved access 97 which has no workaround other than to upgrade.

Current supported upgrades are 2002 and 2003.

2003 appears to use lots 'o system resources, so I am wondering if I am
best to go with the older (2002) version.

Any opinions out here? In particular, which version more likely to make
the conversion of the 97 databases the least painful? Both upgrades
cost the same...

Thanks for any thoughts.

[Lyle Fairfield]

Stephan Golux <st*****@nospam .com.goluxstudi o.invalid> wrote in
news:xd******** ********@newsre ad2.news.atl.ea rthlink.net:

It seems I have run afoul of an unfixable and acknowledged bug in my
beloved access 97 which has no workaround other than to upgrade.
Perhaps, you should tell us about the bug. There are work-arounds for
almost all bugs.
Current supported upgrades are 2002 and 2003.

2003 appears to use lots 'o system resources, so I am wondering if I am
best to go with the older (2002) version.

Any opinions out here? In particular, which version more likely to make
the conversion of the 97 databases the least painful? Both upgrades
cost the same...

Is it possible that you will want in the future some feature that is
available in 2003 but not in 2002?

Software becomes obsolete very quickly. Why start out that way?

--
Lyle
(for e-mail refer to http://ffdba.com/contacts.htm)

[Stephan Golux]

Lyle Fairfield wrote:
<snip>

Perhaps, you should tell us about the bug. There are work-arounds for
almost all bugs.
I have previously written about the bug in this newsgroup - see the
thread titled "Exporting Reports to RTF format causes unexpected
truncation". I have since found a microsoft knowledgebase article that
describes the bug, namely article #288877. URL:

http://support.microsoft.com/default...b;en-us;288877

<snip>
Is it possible that you will want in the future some feature that is
available in 2003 but not in 2002?

Software becomes obsolete very quickly. Why start out that way?

Quite possible, but I am also sensitive to feature and resource bloat.
Access 2003 (by microsoft's published specifications) requires double
the memory of 2002, so I partly want to know if it is worth it. I have
also heard rumors that performance is worse in 2003. Also, since I need
to use a number of databases that were created in 97, I am curious about
whether there are backward compatibility issues I need to be concerned
about.

[Rick Brandt]

"Stephan Golux" <st*****@nospam .com.goluxstudi o.invalid> wrote in message
news:X%******** ********@newsre ad2.news.atl.ea rthlink.net...

Lyle Fairfield wrote:
<snip>

Perhaps, you should tell us about the bug. There are work-arounds for
almost all bugs.

I have previously written about the bug in this newsgroup - see the
thread titled "Exporting Reports to RTF format causes unexpected
truncation". I have since found a microsoft knowledgebase article that
describes the bug, namely article #288877. URL:

The first thing I would do before proceeding is finding someone with a newer
version to absolutely confirm that the RTF problems are solved in those
versions. I am not so sure that they are.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[Lyle Fairfield]

Stephan Golux <st*****@nospam .com.goluxstudi o.invalid> wrote in news:X%
wd************* *@newsread2.new s.atl.earthlink .net:

Lyle Fairfield wrote:
<snip>

Perhaps, you should tell us about the bug. There are work-arounds for
almost all bugs.

I have previously written about the bug in this newsgroup - see the
thread titled "Exporting Reports to RTF format causes unexpected
truncation". I have since found a microsoft knowledgebase article that
describes the bug, namely article #288877. URL:

http://support.microsoft.com/default...b;en-us;288877

<snip>

Is it possible that you will want in the future some feature that is
available in 2003 but not in 2002?

Software becomes obsolete very quickly. Why start out that way?

Quite possible, but I am also sensitive to feature and resource bloat.
Access 2003 (by microsoft's published specifications) requires double
the memory of 2002, so I partly want to know if it is worth it. I have
also heard rumors that performance is worse in 2003. Also, since I need
to use a number of databases that were created in 97, I am curious about
whether there are backward compatibility issues I need to be concerned
about.

I can't imagine buying a new version of Access just to address this problem.

Let's suppose the KB article you cite is correct (they aren't correct very
often but we always have to allow for that possibility). Surely it would be
simple enough to remove double hard returns from the memo field in the
AfterUpdate event of the form where the data are entered, or in a clean-up
type query run before the report is generated.

But, of course, the KB article may be wrong, or not pertinent to your
problem. It's not wonderfully difficult to create a MS-Word file that
contains fields, to fill these fields from MS-Access (I prefer to have the
MS-Word file look for a text file where its field entries reside, and to
create that text file from MS-Access, (automation is another route), and to
send that MS-Word file, or those MS-Word files to whomever, however. And MS-
Access Files can look much better than RTF files, which are quite limited.

Of course, Access97 is a very antiquated program, and you might find many
useful capabilities in a newer version. I use 2000, 2002 and 2003 with no
problems and no noticeable slowness.

--
Lyle
(for e-mail refer to http://ffdba.com/contacts.htm)

[Stephan Golux]

First off, let me say your points are great, and welcome. Just to specify:

Lyle Fairfield wrote:

I can't imagine buying a new version of Access just to address this problem.

Let's suppose the KB article you cite is correct (they aren't correct very
often but we always have to allow for that possibility). Surely it would be
simple enough to remove double hard returns from the memo field in the
AfterUpdate event of the form where the data are entered, or in a clean-up
type query run before the report is generated.
The problem is that the application in question is for people who WANT
that double hard return in the field, and want it to be propagated
appropriately. So removing them is not an option!

But, of course, the KB article may be wrong, or not pertinent to your
problem. It's not wonderfully difficult to create a MS-Word file that
contains fields, to fill these fields from MS-Access (I prefer to have the
MS-Word file look for a text file where its field entries reside, and to
create that text file from MS-Access, (automation is another route), and to
send that MS-Word file, or those MS-Word files to whomever, however. And MS-
Access Files can look much better than RTF files, which are quite limited.

Hmmm... this is an interesting idea, but I would love to pick your
brains for how to apply it in my case.

Basically this application is used by stage managers and directors and
assistant directors in theatre and film who need to create work notes
that are then sent via email or fax to the people who need them.

Essentially, the user types in the notes, and assignes any given note to
any given number of roles, where any number of people may be affiliated
with a given role. Then, once the notes are entered, the user hits a
dingle "distribute " button, and reports are generated for each
individual person, broken down by roles, and then emailed or faxed to
each person automatically. There could be several hundred people and
several hundred roles.

Do you see a way to automate something like this using MS-Word in the
way you describe? I feel like the driving engine needs to be Access in
this case, but perhaps you have experience that would allow me to do
something smarter and cleverer.

Thanks again!

-s

[Stephan Golux]

Rick Brandt wrote:

The first thing I would do before proceeding is finding someone with a newer
version to absolutely confirm that the RTF problems are solved in those
versions. I am not so sure that they are.

Very good point. Thank you.

-s

[Don Leverton]

Hi Stephan,

I haven't read your previous post or looked at the KB article either, so if
what I'm about to suggest is just plain stupid, I apologize in advance.

The implication seems to be that you want to be able to share reports with
other users who may not have Access installed.
Unless your users *have to have* the ability to edit your report, is it
possible that using the freely-distributable Access Snapshot Report Viewer
might solve your problem?

http://support.microsoft.com/default...&Product=acc97

PS. I am also stubbornly "sticking with" Access97. I do have AccessXP, too,
but I just can't seem to invest the time it takes to make the switch. :-(

Another reason for me not to switch is that most of my "clientele" are
automotive repair shops running Pentium / PII / PIII (NOT the newest
equipment) Funny how those guys will spend $6-8,000 on a new "school-bus
yellow" Snap-On (TM) toolbox (and thousands more to fill it with Snap-On
tools), but only $300 for a "good used" PC <grin>

--
HTH,
Don
=============== ==============
Use My*****@Telus.N et for e-mail
Disclaimer:
Professional PartsPerson
Amateur Database Programmer {:o)

I'm an Access97 user, so all posted code
samples are also Access97- based
unless otherwise noted.
=============== ==============
"Stephan Golux" <st*****@nospam .com.goluxstudi o.invalid> wrote in message
news:X%******** ********@newsre ad2.news.atl.ea rthlink.net...

Lyle Fairfield wrote:
<snip>

Perhaps, you should tell us about the bug. There are work-arounds for
almost all bugs.

I have previously written about the bug in this newsgroup - see the
thread titled "Exporting Reports to RTF format causes unexpected
truncation". I have since found a microsoft knowledgebase article that
describes the bug, namely article #288877. URL:

http://support.microsoft.com/default...b;en-us;288877

<snip>

Is it possible that you will want in the future some feature that is
available in 2003 but not in 2002?

Software becomes obsolete very quickly. Why start out that way?

Quite possible, but I am also sensitive to feature and resource bloat.
Access 2003 (by microsoft's published specifications) requires double
the memory of 2002, so I partly want to know if it is worth it. I have
also heard rumors that performance is worse in 2003. Also, since I need
to use a number of databases that were created in 97, I am curious about
whether there are backward compatibility issues I need to be concerned
about.

[Lyle Fairfield]

"Don Leverton" <le************ ****@telusplane t.net> wrote in
news:hwydc.2567 3$J56.13818@edt nps89:

Hi Stephan,

I haven't read your previous post or looked at the KB article either, so
if what I'm about to suggest is just plain stupid, I apologize in
advance.

The implication seems to be that you want to be able to share reports
with other users who may not have Access installed.
Unless your users *have to have* the ability to edit your report, is it
possible that using the freely-distributable Access Snapshot Report
Viewer might solve your problem?

http://support.microsoft.com/default...348&Product=ac
c97

I'm a big fan of the Snapshot Viewer; when it came out I though faxes were
history, but it never seemed to catch on with people. Regardless, if
Stephan could persuade his users to install this, (and it's very simple to
do so) then that would be a much simpler and cleaner solution than messing
with MS-Word files.

--
Lyle
(for e-mail refer to http://ffdba.com/contacts.htm)

[Stephan Golux]

Hi Don - a very creative idea, and many thanks for it. Unfortunately,
to the best of my knowledge this viewer is not available for the
macintosh or for linux. RTF files can be viewed on all those various
machines.

Thanks!

-s

Don Leverton wrote:

Hi Stephan,

I haven't read your previous post or looked at the KB article either, so if
what I'm about to suggest is just plain stupid, I apologize in advance.

The implication seems to be that you want to be able to share reports with
other users who may not have Access installed.
Unless your users *have to have* the ability to edit your report, is it
possible that using the freely-distributable Access Snapshot Report Viewer
might solve your problem?

http://support.microsoft.com/default...&Product=acc97

PS. I am also stubbornly "sticking with" Access97. I do have AccessXP, too,
but I just can't seem to invest the time it takes to make the switch. :-(

Another reason for me not to switch is that most of my "clientele" are
automotive repair shops running Pentium / PII / PIII (NOT the newest
equipment) Funny how those guys will spend $6-8,000 on a new "school-bus
yellow" Snap-On (TM) toolbox (and thousands more to fill it with Snap-On
tools), but only $300 for a "good used" PC <grin>