Connecting Tech Pros Worldwide Help | Site Map

Is it wise to upgrade?

  #1  
Old July 17th, 2006, 02:25 PM
Randy Harris
Guest
 
Posts: n/a
A major application that I develop is currently distributed as an A2K
mde. It uses Oracle for the BE db. The application was upgraded from
A97 several years ago. The users have all been upgraded to Office 2003
and I have been asked to upgrade the application to A2K3.

Are there any compelling reasons to *not* upgrade?

Thanks in advance for your thoughts on this.

--
Randy Harris
tech at promail dot com
I'm pretty sure I know everything that I can remember.
  #2  
Old July 17th, 2006, 02:55 PM
Allen Browne
Guest
 
Posts: n/a

re: Is it wise to upgrade?


By all means, Randy, go ahead and upgrade.

Just do it with your eyes open.

For a list of the sorts of issues you need to be aware of (setup,
conversion, and usability issues), see:
Converting from Access 97
at:
http://allenbrowne.com/ser-48.html

--
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.

"Randy Harris" <please@send.no.spamwrote in message
news:XeMug.6356$2v.219@newssvr25.news.prodigy.net. ..
Quote:
>A major application that I develop is currently distributed as an A2K mde.
>It uses Oracle for the BE db. The application was upgraded from A97
>several years ago. The users have all been upgraded to Office 2003 and I
>have been asked to upgrade the application to A2K3.
>
Are there any compelling reasons to *not* upgrade?

  #3  
Old July 20th, 2006, 07:05 PM
Tim Marshall
Guest
 
Posts: n/a

re: Is it wise to upgrade?


Randy Harris wrote:
Quote:
A major application that I develop is currently distributed as an A2K
mde. It uses Oracle for the BE db. The application was upgraded from
A97 several years ago. The users have all been upgraded to Office 2003
and I have been asked to upgrade the application to A2K3.
I've had zero difficulty converting A97 apps to A2K3. All my apps are
against oracle databases, most using PTQ and DAO, but I did have some
older apps written in the 90s that used linked tables. No trouble doing
a conversion on these either.

All these conversions were just done simply by (first saving a backup)
opening the A97 app in A2K3 and following the conversion routines.

I've almost no experience with A2K, but I can only imagine it would be
just as easy.

Only thing that gave me a minor issue were Oracle DSN connect strings,
and this was, I'm pretty sure, just a case of older installs of the
Oracle client.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me
  #4  
Old July 21st, 2006, 02:35 AM
Randy Harris
Guest
 
Posts: n/a

re: Is it wise to upgrade?


* Tim Marshall:
Quote:
Randy Harris wrote:
>
Quote:
>A major application that I develop is currently distributed as an A2K
>mde. It uses Oracle for the BE db. The application was upgraded from
>A97 several years ago. The users have all been upgraded to Office
>2003 and I have been asked to upgrade the application to A2K3.
>
I've had zero difficulty converting A97 apps to A2K3. All my apps are
against oracle databases, most using PTQ and DAO, but I did have some
older apps written in the 90s that used linked tables. No trouble doing
a conversion on these either.
>
All these conversions were just done simply by (first saving a backup)
opening the A97 app in A2K3 and following the conversion routines.
>
I've almost no experience with A2K, but I can only imagine it would be
just as easy.
>
Only thing that gave me a minor issue were Oracle DSN connect strings,
and this was, I'm pretty sure, just a case of older installs of the
Oracle client.
Allen and Tim,

Thanks very much for the encouragement. This is, by far, the biggest,
most business critical app that I support and I was pretty nervous about
the unforeseen pitfalls of upgrade.

I've read through Allen's issues page (multiple times) and don't see
anything that alarms me. The app is entirely ADO, Oracle connections
are DSNless, and no linked tables. Lots of pass thru's. All binding to
non default libraries is late, so references should be no issue.

I even managed to line up some guinea pigs to test the upgraded version.
Everything looks like a go.

Again, thanks.

--
Randy Harris
tech at promail dot com
I'm pretty sure I know everything that I can remember.
Closed Thread


Similar Threads
Thread Thread Starter Forum Replies Last Post
Visual Studio 6 Enterprise Upgrade to VS 2005 Enterprise =?Utf-8?B?U2hlbGRvbg==?= answers 1 January 8th, 2008 09:55 PM
To link or not to link debbie answers 3 December 22nd, 2005 04:45 PM
When should you upgrade access 97/vba applications? Terry Bell answers 6 November 13th, 2005 09:18 AM
Best way to handle distributing runtime installables from the web??? (slightly O.T.) MLH answers 5 November 12th, 2005 05:53 PM