David W. Fenton wrote:[color=blue]
> Bob Alston <tulsaalstonsNOSPAM@cox.net> wrote in
> news:wSkwe.5516$4o.3588@fed1read06:
>
>[color=green]
>>David W. Fenton wrote:
>>[color=darkred]
>>>Bob Alston <tulsaalstonsNOSPAM@cox.net> wrote in
>>>news:Sjiwe.5129$4o.4772@fed1read06:
>>>
>>>
>>>
>>>>Take a look at the info I collected on this subject:
>>>>
>>>>
http://members.cox.net/tulsaalstons/...soft%20Access%[/color][/color]
>
> 2
>[color=green][color=darkred]
>>>>0 Developer%20Transition%20to%20Internet.htm
>>>
>>>
>>>That's a good article that I'll bookmark, but it seems to me to
>>>be handicapped by the failure to clearly distinguish between
>>>Access and Jet. You keep using the term "Access" for cases where
>>>the MDB file is being used only as a data store. That just makes
>>>the whole issue more confusing.
>>>
>>>For all practical purposes, there isn't any way to use an Access
>>>application on the web (this is basically what you say).
>>>
>>>But there are plenty of ways to build web applications using a
>>>Jet MDB as your data store.
>>>
>>>That said, let me emphasize your point about knowing the hosting
>>>environment: I don't use Jet for any web development because I
>>>don't think Windows is suitable for a web server, except on an
>>>Intranet. The only valid hosting environment, in my opinion, is
>>>with Apache as your web server. That means no real ASP
>>>development, and mostly no Microsoft server technologies.
>>>
>>>I'm fine with that.
>>>
>>>Other people aren't.
>>>[/color]
>>
>>While I agree that my approach of using Access as a database
>>server within Windows is primarily only using Jet, I would not
>>know how to deploy jet directly to accomplish this same thing,
>>except by storing an MDB file on the server.[/color]
>
>
> Since you're not installing Access on the server, you're *not*
> deploying Jet. If the web host supports MDBs (they will probably say
> "we support Access databases" when what they mean is "we support Jet
> databases"), they already have JET installed.
>
> Making an MDB with Access does not automagically carry with it the
> Jet database engine. A server that has neither Access nor Jet
> installed on it won't be able to read the data tables in your
> Access-created MDB.
>
>[color=green]
>>Regarding Windows not being an appropriate place to build web
>>apps, I strongly disagree. My IT team built a large web
>>application using windows servers (many of them) which did $100
>>million in business in its first 100 days. Of course, it did not
>>use an Access database but rather SQL and interfaces to a
>>mainframe.[/color]
>
>
> I strongly disagree on Windows as an appropriate web server. The IIS
> disasters of the past couple of years show that Microsoft doesn't
> know what they are doing in regards to security.
>
> Likewise, I have found Windows hosting to be more expensive than the
> corresponding non-Windows hosting.
>
> I started out getting into this by learning Cold Fusion. It was
> great -- I was up and running with a useful Web application in 8
> hours, including download/install time. But then I couldn't find a
> suitable host for it.
>
> I eventually switched to PHP running on Apache. It's not as easy for
> me as a VBA programmer, but it runs almost everywhere, and there are
> literally hundreds of choices for inexpensive hosting.
>[/color]
David -
Thanks for the clarification. I think I get it now.
I was incorrect to say that one would "deploy jet" in a web
application; equally incorrect to state that one would use an Access
database in a web application, even if one were to create tables and
queries using Access and saved into an MDB file and access it via a web
application; I should have more correctly stated that one would "build
web applications using a Jet MDB as your data store".
Bob
