> > Do you think it is easier to write/maintain forms in Access
> > than in CFML/HTML?
>
> No, but I don't really think it's harder, either.
The poser of the Access solution suggested that doing it with CFML
(instead of Acess/Excel) would be reinventing the wheel. I suggest
that it would be a wash.
> and I've never
> seen a "locked db" problem within a single-user Access application,
> as long
> as the database itself is writeable.
I have seen this if Access or the system crashes -- I have seen quite a
few times and I have never used Access in a multi-user application.
But, If Access is a mandate, you could use it as the db component of a
Win-Only CF Desktop solution -- though there better dbs available.
>
> > And, IMO, CFAnywhere would be a superior solution -- in
> > almost every way!
>
> Since I'm diametrically opposed to your conclusion - I think it would
> be
> worse in almost every way - I'm curious about the reason for your
> bias.
I'll quote the originator of the thread:
"
I've been tasked with building an app for engineers on the road to
report how cell phones function. Unfortunately they wont be connected
to the internet while on the road. So I'm guessing my only option
would be to build something in Java, VB, ASP or something to record
the data in an Access DB to upload at a later time to an Oracle DB.
The Admin section would be in CF tieing to the Oracle DB.
Does anyone have any other options, ideas or comments.. Anything is
appreciated.
"
Since he posted to a CF list I assume that a major part of their
installation is CF
He suggests that because the application is not connected to the
Internet, he must look at non-CF options to write the application.
And it appears that these options (Java, VB, ASP or something) are less
desirable to him than CFML (for whatever reasons).
He does state that the online (Admin) section of the app would be in CF.
So, here are the reasons for my bias:
1) Given the above, he *can* do the entire app in CF -- rather than
clutter the implementation with other languages, GUIs, spreadsheets, or
Access forms.
2) It is a cheaper, simpler, cleaner solution for the implementor and
for the user (who uses the ubiquitous browser interface that MS so
eloquently insisted is part of the win OS.
3) And, over time, as the application maintained/upgraded, it be
deployed by the users with a simple download or copy/paste -- no other
installation necessary by the users.
4) I think that this is a natural extension of CF's capabilities
I suspect that you won't agree, but appears to me that a CFAnywhere
solution is all upside with little downside risk.
Dick
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
