RE: [AccessDevelopers] What are the benefits of Access over Excel??

[Craig Gross]

My two cents:   Like many here I program in Excel as well as Access. I also work with someone who codes in Excel, but doesn’t have the first clue about Access. When I told him that many of the things he was working on should be in a database, he looked at me in a funny way. The reason, from my point of view, has to do with the complexities of database design compared to Excel where it is easier to learn VBA. He can record macros with Excel, see the code, and edit it, but this process is not easily repeated in Access.   There is little doubt that Access holds advantages over Excel when storing data. Let’s face it that is what it is for. Look at this way, is Oracle well known for a spreadsheet program? The Excel programmer looked down on Access, but this again has to do with the unkown terrain. However, once he saw what could be done in Access he wanted to know more.   You need to learn about database integrity as well as good design. Think of ways to build multipe tables so as to avoid redundancy, and link ID fields. Create queries to bring your data together, and when you do all that you can take your Excel knowledge and integrate it with the database to create some awsome reports, and then some…J     -----Original Message----- From: AccessDevelopers@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of wall_street24 Sent: Thursday, August 25, 2005 6:18 PM To: AccessDevelopers@yahoogroups.com Subject: [AccessDevelopers] What are the benefits of Access over Excel??   After years of using Excel to store data, I decided to try out Access. Last week my database got corrupt; and now, some questions have come to mind (so I've decided to "ask the experts"): First and foremost, what is the advantage of using an Access database? (I mean, if I put the same information into Excel, it seems I can always create a formula to define parameters that I might need; and an Excel file is a fraction of the size.) And of course, I need some pointers: In creating an Acceess database, should I put ALL my information into a 'master' sheet, and then create queries to filter for required information, or am I better off using several smaller tables. Initially this started out as a simple idea to record contact information of business.  Then, a subform seemed logical to store additional information on employees of each individual business. What would be your suggestiions? Unfortuneately, the Access books that I've seen, concentrate on implimentation, and NOT practicality; so your recommendations are welcome. Thanks. This email and any attachments contain information from Baker & Taylor which may be confidential, privileged and/or protected by other legal rules. If you are not the intended recipient, you are hereby advised that any disclosure, copying, distribution or use of the contents of this email is prohibited. If you have received the email in error, please notify us by reply email immediately and then delete the email and your reply from your email system. NOTE: Baker & Taylor accepts no liability for the contents of this email. This email shall not operate to bind Baker & Taylor to any contract, order or other obligation. Please zip all files prior to uploading to Files section. SPONSORED LINKS Microsoft access database Microsoft access developer Microsoft access Microsoft access database design Microsoft access database training YAHOO! GROUPS LINKS  Visit your group "AccessDevelopers" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.