That's a strange way of doing it - it's usually the other way round.
You shouldn't find any problems doing this - msde is just like the personal edition without the client which is like the server edition with a few facilities removed (multi-processor, thread goverend, ...)
Thanks for your answer, I feel more comfortable now with MSDE. But you made a remark:
>> That's a strange way of doing it <<
>> it's usually the other way round. <<
Coming from the Guru, this is certainly a sign of trouble. What do you have in mind ?
On reflection, it could well be my fault = I wrote stored procedures for years, and now I'm upsizing an Access Project. I've found the client tools on another CD, and I'm using isql with MSDE. Seems to be working.
Having a .BAT to recreate the database is an extra precaution. The database will eventually be deployed at a different location, and I will need to do it very fast, when time comes.
Thanks for your answer. I'm fairly new with the Microsoft product line, but I've been doing client-server for a long time. Again, you made a remark which makes me cautious:
>> want to distribute using msde <<
My intention is to deliver a client-server application, where all users connect to the same instance of the relational database. So, we only intend to distribute the Access ADP file, but not the MSDE. Please let me know if this plan sounds feasible.
At this stage, the equipment and the infrastructure is not ready yet, that's why I'm developing on my home machine. Within a month, we'll go the full size with Sql 2000 server, and ten users (at most three running simultaneously) on the Lan. Will Sql 2000 fit the purpose ?
Needless to say, this started as a low-budget Access project, so compromises are possible. BTW: I'm delighted with the small footprint of MSDE. I'm also impressed with the client tools, and the programmer -friendly features MS has added to the old Sybase Transact-Sql.