Replacement for Access 97

[Pradeep]

Hi all,

One of our customers who has been using Access 97 for a long time has
made a strategic decision to move to Oracle 10G. However, they are used
to the simplicity of creating forms and defining business rules in
Access. I am wondering if anyone knows of a commercial product on
Windows that will let you easily define business rules and create forms
with the simplicity of Access.

Thank you in advance for your help.

Pradeep

[(PeteCresswell)]

Per Pradeep:

I am wondering if anyone knows of a commercial product on
Windows that will let you easily define business rules and create forms
with the simplicity of Access.

Why not just point MS Access at the Oracle tables?
--
PeteCresswell

[Saintor]

"Pradeep" <pr*****@tapadiya.net> wrote in message
news:11*********************@g44g2000cwa.googlegro ups.com...

Hi all,

One of our customers who has been using Access 97 for a long time has
made a strategic decision to move to Oracle 10G. However, they are used
to the simplicity of creating forms and defining business rules in
Access. I am wondering if anyone knows of a commercial product on
Windows that will let you easily define business rules and create forms
with the simplicity of Access.

Short answer: no. Even Access 97.

[pietlinden]

Most effective/efficient answer is probably to create stored procedures
and triggers in Oracle to enforce your business rules, and then call
them in your Access FE.

Hey, converting to Oracle isn't that easy. That's the cost of power, I
guess.

[Pradeep]

Thank you all for your help. After going through the requirements
carefully, we proposed using Visual Studio 2005 for rapid form
development and the customers has accepted the proposal.

Pradeep

[Terry Kreft]

Maybe you missed the anawers you were given... use Access.
--

Terry Kreft
"Pradeep" <pr*****@tapadiya.net> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...

Thank you all for your help. After going through the requirements
carefully, we proposed using Visual Studio 2005 for rapid form
development and the customers has accepted the proposal.

Pradeep

[lesperancer]

oracle also has a development suite, oracle forms / reports that is
integrated with their environment

[Tim Marshall]

Terry Kreft wrote:

Maybe you missed the anawers you were given... use Access.

I agree.

If your customer is proficient with Access (and I'd recommend going to
2003 from 97), why not simply structure the database in Oracle and use
Access to write the forms? You can use the Jet SQL dialect using ODBC
linked tables or you can use Oracle SQL using pass through queries (my
preference) or even ADO (however, ADO falls short in writing reports in
the mdb reports collection).

There are a number of us here who use Access with oracle quite regularly
and would be happy to help as we can with any challenges you/your
customer may encounter.

Whether one uses Access/Jet or another database engine, the design steps
in determining and mapping out a structure and corresponding constraints
(relationships) is quite similar.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me

[David W. Fenton]

"Pradeep" <pr*****@tapadiya.net> wrote in
news:11**********************@o13g2000cwo.googlegr oups.com:

Thank you all for your help. After going through the requirements
carefully, we proposed using Visual Studio 2005 for rapid form
development and the customers has accepted the proposal.

How idiotic.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Larry Linson]

"David W. Fenton" wrote

Thank you all for your help. After going
through the requirements carefully, we
proposed using Visual Studio 2005 for
rapid form development and the customers
has accepted the proposal.

How idiotic.

David confirms again that he is not always tactful, but is very perceptive.

On the other hand, we have not gone through Pradeesh's customer's
requirements carefully -- it could, perhaps, be a humungous, intergalactic,
enterprise web-based application, for which VS would be better than Access.

"Rapid form development" does not necessarily imply Rapid Application
Development (RAD). I have seen no examples indicating that Visual Studio is
a useful tool in the area that we have come to call "Rapid Application
Development" (RAD), when compared with Access as a front-end that can be
linked to different backend databases.

Larry