>>>
>>>I thought one of the reasons that Jet was still going to be around was for backward compatiblity. It would be nice to have a real good benchmark to show which it is the best engine to use. Maybe one of the magazines will do some comparisons.
>>
>>I think it is a given that there will be a Jet vs MSDE debate and comparisions. I understand that it will be marketed as "if you have existing Access applications, use Jet, otherwise use MSDE"
>
>I just picked up a copy of Access, Office, and VB Advisor for June 1999, and Stephen Forte, contributing editor asked the same question. His response is to learn and use both. He also says "The licensing structure of SQL Server and scabability of SQL Server desktop still leaves room for Jet." He then goes on to say "SQL Server Desktop could be an alternative to Jet; however, the maximum number of users Microsoft recommends for optimal performance is three. Any more than three users and you need the full-blown SQL Server running on top of NT Serverm which requires NT Server and SQL Server client licences--not to mention the LAN and DBA support. With Jet, you won't need licences if you use Visual Basic or the ODE to distribute applications."
>
>Another interesting quote that Stephen say is "When SQL Server 7.0 links to ISAM data, it uses Jet."
>
>The only time he mentioned MSDE is if you are developing on Windows 98, off site, or not connected to the SQL Server database, using a SQL Server application with an Access 2000 front end. Then you can design the database using MSDE locally, then smoothly move the database to SQL Server.


Thanks for that reply. I'm going to pick up a copy just for future reference.