Stan,

My knee-jerk reaction is to say 'No'. By supporting Access, you could be 
propogating the myth that Access is a sufficient databse to use for web 
applications. In my opinion, Access would never be the DB of choice, other 
than to track my DVD collection...but I would never look at it anyway, so 
why bother. 

After some thought, though, if it does not warrant a lot of development 
time, maybe you should. Here is an anlogy.

Let's say I make golf balls. Would I want to design a golf ball that only 
works with pro-line golf clubs? Probably not. I would want it to work well 
with any type of equipment. 

After all, can one play golf with the $50 complete golf club set (with bag) 
from Wal-Mart? Yes. Is it more advantageous to use better equipment? 
Absolutely.

Can one use Access for a web application? Yes Is it more advantageous to use 
a better DB? Absolutely.

While Access may be misused as the backend for web applications, it is also 
the starting of point for a lot of developers, it might not be a good idea 
to segregate that part of the population.



On 6/7/05, Stan Winchester <[EMAIL PROTECTED]> wrote:
> 
> As many of you know from my previous posts we have had a forums 
> application
> in beta testing for a while. It was developed primarily using SQL Server 
> and
> MySQL, but wanted to offer support for Access & PostgreSQL, but have found
> Access a pain to support. The problem is with cfqueryparam throws errors
> with Access because the cfsqltype in many cases is not the same for Access
> as it is for the other databases. For example:
> 
> 
> 
> Using a data type: "number" field size: "Long Integer" throws an error
> "Database reported: [Microsoft][ODBC Microsoft Access Driver]Optional
> feature not implemented" if the cfsqltype is "CF_SQL_INTEGER". If I change
> the cfsqltype to "CF_SQL_NUMERIC" it works fine.
> 
> 
> 
> Another example:
> 
> A SQL Server, MySQL, ect. field data type varchar(500) with cfqueryparam 
> set
> as follows: <cfqueryparam value="#Comments#" cfsqltype="CF_SQL_VARCHAR"
> maxlength="500"> works fine in SQL Server, MySQL, ect., but breaks in
> Access. If I remove the maxlength="500" it works.
> 
> 
> 
> I know most will agree Access is from the database of choice, so my 
> question
> is should we support Access considering the challenge, or drop support? To
> be honest, I cannot imagine a forum actually being used in a production
> environment using Access.
> 
> 
> 
> Thank you,
> 
> Aftershock Web Design, Inc.
> 
> by: Stan Winchester
> 
> President/Developer
> 
> [EMAIL PROTECTED]
> 
> http://www.aftershockweb.com/
> 
> Phone 503-244-3440
> 
> Fax 503-244-3454
> 
> 
> 
> 
> 
> 
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Discover CFTicket - The leading ColdFusion Help Desk and Trouble 
Ticket application

http://www.houseoffusion.com/banners/view.cfm?bannerid=48

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:208828
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to