Solved

From Excel to Access - Good Arguments

Posted on 2013-06-24
6
233 Views
Last Modified: 2013-07-08
I'm considering moving the data we stored in our big Excel workbook to Access.
The existing workbook has 15 worksheets, 10 userforms and almost 5500 lines of code and it's getting bigger and bigger - and more complex. That's why I think it's time to move ahead.

Unfortunately, our company is reluctant to use Access. Maybe because it's too difficult (it's a database?!) or because of security concerns (it uses Macros!). I'm not sure.

I need to convince my boss that it's time to use Access. What are some good arguments which I can use?

Massimo
0
Comment
Question by:mscola
  • 3
  • 2
6 Comments
 
LVL 75
ID: 39273061
Well .. Access is a real database application platform. Excel is not.

"or because of security concerns (it uses Macros!)"
Macros ?

However, IF ... security IS  of prime concern, then you should look at SQL Server - but you still have to create a Front End (UI) ,,, and Access could still be that tool.

mx
0
 

Author Comment

by:mscola
ID: 39273115
To be honest, I think that saying that macros can cause havoc is just a false pretenses.
My existing Excel spreadsheet makes extensive use of Macros. Some of them write to the file system and create HTML pages. Saying that Macros/VBA code written with Access is a security concern is a claim not supported by facts. As otherwise my supervisors and the guys in charge of IT would have hindered me to use VBA in Excel.

What are some good points which I can tell my boss/IT guys why it's time to use Excel.
0
 
LVL 75

Accepted Solution

by:
DatabaseMX (Joe Anderson - Access MVP) earned 350 total points
ID: 39273204
In Access, VBA code and Macros are not the same thing.

"Saying that Macros/VBA code written with Access is a security concern is a claim not supported by facts"
No serious Access application can be w/o a  LOT of VBA code. The only Macros I use are AutoExec and AutoKeys.

"Maybe because it's too difficult "
Of course, that is very subjective.

Other  reasons.
You cannot create a Relational Model in Excel, let alone implement Referential Integrity.

"it's getting bigger and bigger - and more complex. "
Consequently much more unwieldy and harder to maintain.
And I'm sure the Multi-User aspect is not the same.
0
Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

 

Author Comment

by:mscola
ID: 39273325
You wrote that VBA code and Macros are not the same. What is the difference?  

I noticed that if I normalize too much, it will be harder to create reports. But that's something I need to look at.

As Pivot Tables have been dropped in the latest version of Access,  we would still use Excel for creating the charts. Do I need to import the orders into Excel for creating the charts, or can the data stay in Access?
0
 
LVL 74

Assisted Solution

by:Jeffrey Coachman
Jeffrey Coachman earned 150 total points
ID: 39287750
<You wrote that VBA code and Macros are not the same. What is the difference?  >
A macro in Excel *IS* VBA code, they just call it a Macro in the Excel world.

In Access you have a Macros *and* VBA code.
In Access, a macro is a separate "Language" from VBA and has it's own interface.
Macros in Access have advantages and disadvantages.
To keep it simple, ...VBA in Access is more versatile than a macro in Access.

"The existing workbook has 15 worksheets, 10 userforms and almost 5500 lines of code and it's getting bigger and bigger - and more complex. "
...This is always a scary statement to hear in the Access zone.
;-)
We have seen countless spreadsheet with such "unique" (for lack of a better word) designs that it is nearly impossible to duplicate them directly into Access, in a truly "Normalized" design.
There will probably be very little of your existing code that can be salvaged...

Without a sample of the spreadsheet though, we are flying totally blind here...

JeffCoachman
0
 

Author Comment

by:mscola
ID: 39306903
Thanks a lot guys for your information.
I had a closer look at Macros/VBA and they are indeed different.

The next step for me is to analyze the data and to create a data model.
I don't mind if the Excel VBA code cannot be ported over to Access.

It's more important that the data is stored in a database.
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

When you are entering numbers in a speadsheet, and don't remember what 6×7 is, you just type “=6*7" instead. It works in every cell! This is not so in Access. To enter the elusive 42 in a text box, you have to find a calculator, and then copy the re…
In a multiple monitor setup, if you don't want to use AutoCenter to position your popup forms, you have a problem: where will they appear?  Sometimes you may have an additional problem: where the devil did they go?  If you last had a popup form open…
Learn how to number pages in an Access report over each group. Activate two pass printing by referencing the pages property: Add code to the Page Footers OnFormat event to capture the pages as there occur for each group. Use the pages property to …
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

24 Experts available now in Live!

Get 1:1 Help Now