To use Excel or Access

[paris1979]

Hi, I've managed to create it in excel but wondering if it will be more stable/user friendly in Access.
I have a database with all the prices for parts, purchase cost of items, selling prices and other costs.
It is saved on sheet1, on sheet 2 I have a table set so when a user needs to know if it is worth adding parts to a device for repairs, as he ticks the relevant boxes it adds all the different values in the background, soon as the resale value is reached by adding parts to the device, the name change from green to red to let the user know it's not worth repairing the device anymore.
I hope it makes sense.
Thanks
Nico

 

[oleronesoftwares]

It depends on a few things. Since you said it worked in excel

1. Are you better at coding in excel or access, if u are better in excel, then retain it in excel.

2. Do you envisage using multiple sheets in the future, if so, then access is a better option

3. Will there be many reports to be gotten from the file in future, if so, access is better

 

[paris1979]

Hi, thank you for your quick answer. I have very little knowledge of Access.

At the moment, probably about 5 sheets, each one is for iPhone model, each sheet will have all models and sizes for that specific generation(8, X,11,12,13).

I won't need to run reports from it, it's to be used as a quick cost/value checker.

But like I said I have little to no skill on Access, I'll stick to excel.

Thank you for your reply

 

[GPGeorge]

This sounds like the kind of analytical function that Excel excels at. Access can be programmed to do similar calculations. However, unless you're trying to save a history of repair/discard decisions, Excel is probably a more useful tool for this.

 

[paris1979]

Thanks, I wanted to be sure I was going to use the right software before going further into setting it up in excel.

Thank you

 

[theDBguy]

Hi. Welcome to AWF!

My vote would be to use Access, but that's only because I rarely use Excel, and I really have no idea what your Excel workbook does.

Good luck!

 

[Mike Krailo]

I have a database with all the prices for parts, purchase cost of items, selling prices and other costs.

You can certainly use Excel as a database to some extent, but if you need to do anything relational, then Access would be better. But it sounds like your doing calculations based a table of part prices for each phone. How hard is it to add all the part prices for a new version of a phone? How many parts and prices are we talking about? I find it hard to believe there are that many replaceable or repairable parts in any given phone so maybe your Excel App will work just fine as is.

If there is a particular website that supplies the parts and prices, maybe you can link to their data or scrape the info right off of the website into your app to keep all the price data current.

 

[Cronk]

Stick with Excel if your current set up does all you want of it. If you add enhancements, you will find eventually Excel cannot handle it. Over time, I've been given the commission to convert a number of Excel solutions into a relational Access database to handle additional requirements, especially management reporting.

 

[Pat Hartman]

It sounds like this is simply a calculator. You are not storing data. You are not looking to report on any past activity. So, there is no pressing need to convert the application. If you are the only user, you can do what you want but I would create a template and use the template to perform each new calculation. That minimizes the danger of something being accidentally changed.