Peter J. Boettcher — Fri, 12 May 2000 20:16:00 +0000

KLWong,

Maybe the best thing to do is to keep your Master database in Access format and just import it when it changes, into SQL 7. To do this you would need:

1) Access on the master computer
2) Enterprise Manager on the master computer
3) SQL Server on the Web Server

Importing is fairly easy using a wizard, or if you're comfortable you can use a SQL statement.

This would work if there's no issues with script timeouts on the master computer (it sounds like you don't use the DB for web stuff on the master computer).

Regards,
Peter J. Boettcher

KLWong — Fri, 12 May 2000 18:53:00 +0000

Sorry to take so long getting back, but thanks for your answer!

The way I am managing my database is by keeping a "master" on my personal hard drive and uploading copies to my website whenever the data changes. Since the database content never changes except in the master, this workaround would only mean that I'd be uploading several copies at a time, instead of one.

Also (correct me if I'm wrong), wouldn't I need to buy a copy of SQL Server to continue with this "master at home, copy on the web host" paradigm? Could I do maintenance and everything on the local master database without it, or is that what the Enterprise Manager does?

------------------
http://www.RewardsLookup.com

Peter J. Boettcher — Mon, 08 May 2000 18:35:00 +0000

KLWong,

1) You'll know you're starting to have problems when your scripts start timing out, due to the fact that Access is busy with to many other users.

2) While this would would work, it sort of defeats the purpose behind a central db. Will you be synchronizing these databases so the data is the same in each?

You don't really have to "buy" SQL Server. As long as your host installs the server portion, all you need is Enterprise Manager (part of the client install). You can get a SQL Server 7 evaluation copy and just install the client tools, I don't think the client portion ever expires.

Regards,
Peter J. Boettcher