Actually in the long run it is not easier... if it seems like it might turn into a medium or big project the headache of trying to maintain an Excel spreadsheet program becomes larger and larger. And while Access is better and generally cleaner it to gathers a level of complexity that can be problematic as a project gets big. So in short Excel for small rather simple solutions, Access for medium solutions, and then an actual coding language for when anything that seems like it might ever get too big. Note for the latter you simply use a more VBA version of Access and separate the database from the frontend to emulate a VB which is only one step away from using actual VB or VB.Net. Most programmers should be able to convert a VBA frontend into a more robust and cleaner program provided you do not tie things directly to the database and use SQL queries from within code instead.
Another word of warning what seems like a small simple solution now can grow into a major and complex problem latter on. Since most things grow I'd suggest starting with Access if you feel it won't get too big. If you think it will get heavy use, then I'd suggest VBA from the get go. --- On Fri, 3/27/09, woody_woodz <[email protected]> wrote: From: woody_woodz <[email protected]> Subject: Re: Bls: [Access VBA Central] please allow me to know... To: [email protected] Date: Friday, March 27, 2009, 11:14 AM I know this is an access group, but I think it might be easier to use a form created with excel, if your goal is to modify the xls file, or do calculations or whatever in excel. Regards [Non-text portions of this message have been removed]
