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