"Duane Phillips" <askme@askme.askme> wrote in message
news:-rqdnfP01JFM9u_eRVn-rw@giganews.com...
> Victor,
>
> You are confusing JET with Access. They are not the same thing.
> You can use Access as a front end tool to nearly any type database.
>
> That includes MS SQL Server.
> That includes MySQL, Oracle, DB2, FOX Pro, CSV files, Excel sheets, etc.
>
> It does not matter where DB server is, just so long as you can access it.
> The rest is just details.
>
> Your statement is very telling:
> "Now, compared to MS SQL, which is on a seperate server. The only way to
> view & modify the database is by SQL commands - I can't directly view the
> database."
>
> It appears you do not know the joy (and and sometimes the pain) of server
> class DB systems. Once your user count and concurrent transactions hit a
> certain level, JET is no longer an viable option.

I understand this, and I've heard all about how JET can't handle high volume
transactions, but in reality, even with 230,000 monthly visitors I've had absolutely no
problems. If I ever do have problems, I'll just cache the database calls & I'm good to
go.

>
> But you still have not described anything about your DB needs.

I've already described what I need. My main need is TIME. I want to save TIME. With JET,
with an Access database *directly* accessible on my shared server via FTP I can view &
modify the database instantly. That's what I want. That is my main need. The technical
details I can more than handle.