[AccessD] A97 BE with A2k3 FE

Been running a similar scenario for a year now on a test management
system that uses both an A97 (Jet 3.5) back end which is also used by a
Jet 4.0 third aprty app, and a A2k "mid end" and both an A2K and an A2k3
front end.  The only problems I have found have been forgetting where I
was and making changes to the UI in A2k3 which are not compatible with
the A2k fromt end.
Sound strange?

The back end is a UML model repository that we use to design the tests.
It's a Jet db that starts life as an A97 db and gets used by the UML
tool from http://www.sparxsystems.com.au (no relationship - highly
recommended) via Jet 4.0, when we move into test execution stage we use
a home-grown results recorder which I use on an A2k dev machine, the
test lead uses on an A2k runtime machine and every time I go home I
think of something else we could do and dev it up on A2k3.....

I have on occasion also taken the db's home and up-and-down-gradeded
them to A2k3 and back to "prev" without any ill effects.


.... Just lucky I guess  :-)

Hth
Bruce

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Bartow
Sent: Wednesday, 16 November 2005 4:08 PM
To: _DBA-Access
Subject: [AccessD] A97 BE with A2k3 FE

Anyone have any experience with using an A2k3 FE with and A97 BE?
 
I've been testing it for a client request and haven't had any problems
yet but would like to hear of others experiences.
 
TIA
John B.

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com





This e-mail and any attachments may contain confidential information that is intended solely for the use of the intended recipient and may be subject to copyright. If you receive this e-mail in error, please notify the sender immediately and delete the e-mail and its attachments from your system. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient. Any opinion expressed in this e-mail and any attachments is not an opinion of RailCorp unless stated or apparent from its content. RailCorp is not responsible for any unauthorised alterations to this e-mail or any attachments. RailCorp will not incur any liability resulting directly or indirectly as a result of the recipient accessing any of the attached files that may contain a virus.