access front end

[forrest lyman via AccessMonster.com]

I am almost finished building an application in access vba which i intend
to use as s front end for an sql server database. I plan on keeping a good
amount of the data on the clients desktop with the mdb application.
Monthly the client will upload a selected group of data, which will be
appended to the sql server database. This data will be accessed online on
my website (by the company investors, etc). I just read a number of
threads on another website bashing access development. I have a number of
companies interested in the application, and expect the number to grow. Am
I getting myself into trouble distributing an application written in access
vba?
Any thoughts or experiences would be much appreciated

 

[richard hedrick via AccessMonster.com]

Forrest i dont think we can ever get away from the "my development tool" is
bigger and better than your development tool mentality of some developers.
The fact is there are many situations where, IMHO, Access is a much better
choice if what we are wanting to accomplish is provide the customer with
the best and most cost effective solution and not just boost our egos. I
started using Access with version 2 and moved on to VB then VB.net but
still find that for many situation Access is the perfect solution
especially if your users already have Office on their PC's, even if they
dont the runtime is much improved over earlier versions. I have some
Access(ADP)/SQL apps that can have as many as 50 concurrent users and over
500,000 records in a single table, they are stable and very responsive. I
dont think Access can be automatically ruled out as a possible solution to
some users needs.

I was just trolling around for a solution to a specific problem so i might
not remember to check back on this thread so just email me (reg[at]
elccweb.com) if you want any additional info.

HTH
richard