Hi Emma,

It's nice to see someone ditching Oracle for SQL Server 2000.

My recommendation is to keep things simple for a start and that means MDB. The following are my reasons:

1. Creating queries in Access is a piece of cake. Since this is a large part of what the user will do, it may be appreciated.

2. Views that you create in SQL Server that have a high probability of being used, can be linked as tables to save on network traffic.

This will get their feet wet and then you can switch them to ADP.

If you work with them to create queries that invovle other queries which in turn involve other queries, this will minimize network traffic to the final record set. My problem is that I never used ADP. You can do the same things using MDB/MDE linked to SQL Server. Whatever I need to do on SQL Server I do with the Enterprise Manager and the Query Analyzer directly. If I have complex query chains, I put all of them on SQL Server. Also since user defined functions came along, you can do virtually anything this way.

Just a thought.

Mike