Is Microsoft Access 2007 any use?

[purplemonkey]

Does anyone use Microsoft access?

If so what for?

Is it easy to learn to use?

Why not just use Excel 2007?

[Gillie]

Erm because Access does so much more than excel! If you have a logical mind then yes Access is quick to pick up!

[Astaroth]

They are two very different packages which is why you dont just use one or the other. Same as why people buy both lemons and oranges, both are citrus fruit but wouldnt want freshly squeezed lemon juice with my morning breakfast.

I've always found Access to be a bit too much of nothing, either you have it in mode 1 which is overly simplified and you cant really do a lot of things or you have it in mode 2 where you dont get even the most basic of hand holding where as other systems even though technically more professional have some middle ground between the two. Saying that I havent looked at 2007 to know if it has improved or not.

[purplemonkey]

Thanks for the reply guys...

ok perhaps I'll rephrase the question... So what do you use access for to help run your ecommerce business?

I know what I can use excel for, it's great with numbers statistic etc. but access is an unknown quantity for me and seeing as though i have access 2007 sat doing nothing I thought I should ask!

Cheers

[Astaroth]

To be honest it depends what you have on your ecommerce site.... it will almost certainly be running off a relational database like MySQL. Access is basically the same other than 1) it has a user interface where as SQL servers dont (though there are plenty you can get) and 2) the files are more easily portable.

If your ecommerce package doesnt have much statistical analysis or CRM etc you could connect Access and the SQL server so that you can create new queries to get management information out - eg if you were to add a new product you could use access to identify all those that have purchased a related product to then email them to advise that they bought X on 4th Jan and now you can offer them the new Y for it etc.

Excel is manipulating flat data, Access is querying relational data.... there is a cross over as you can use a db for viewing flat data and pivot tables can do basic data mining but both have their expert areas

[sm1]

Hi all,

I am wondering the same too.... what I find is that with Access you can build a database etc. but then after it's built and all complete, you still have the tools at the top to create a new form etc. so it's not like you've built a programme and you can use the database as a stand alone CRM, but it's as though the database you've created runs in the same area that you use to make it...

Hope you understand!!

Cheers :D

[Tom McClelland]

In general loads of people use Excel for all kinds of things that would be better done using Access. Presumably because they have difficulty getting their heads round the more rigorous data definition requirements that Access has from day 1, before you can start to achieve anything with it. Once you've understood what Access is for and how to use it loads of the tabular data that people typically try to manipulate in Excel spreadsheets is far better handled using Access.

[purplemonkey]

Could you use access to construct a product catalogue which could then link into a website?

[brownie]

I wouldn't use access as a website backend, something like MySQL, MS SQL Server, etc. are more scaleable and robust. For example the security on an Access database is weak.

I use Access in the office for a customer database.

[Astaroth]

You can use Access as an OKish front end to SQL Server and potentially MySQL (its been a long time since I have used it) but it isnt ideal for it. To be honest I think its days are fairly numbered now that there is MySQL, SQL Server and Oracle that all offer free versions of their software that is more than enough for most SMEs. Only one of them needs to offer a user friendly front end and it will be the final nail in the coffin..... there are plenty of front ends but they are much more aimed at semi-developers+ than skilled business users

[consultant]

the uses of databases and spread sheets, although similar, are not the same.

The best thing is to work out what your task or problem is and then apply the correct solution.

[brownie]

I think Access is fine as a frontend into a MySQL/MS SQL DB, some nice forms/apps can be knocked up. It's just that I wouldn't store a load of business critical data in an MDB file.

1. Access<----(ODBC)----->MySQL/MS SQL<---------->Website - OK

2. Access<---------->Website - Not the best idea

[sm1]

Cheers all :D

[Steve2507]

We use Access for most of our backend.

All our stock is held in it, we enter or takings in it, postage costs, I keep records of what products have been pro-actively marketed and when, suppliers orders are generated in it, disk codes are held in it (the ones you get on the stickers on CDs), back ups of articles, back up of customer data, assets. Basically everything we need to run our business is in our Access db.

Our site runs on MSSQL and using Access means we can easily enter the new details in Access and then import it into MSSQL.

As others have previously said Excel is a completely differnet package and is designed for comletely different uses than Access.

[sm1]

What does anyone use as a front end? As Access does not have an amazing interface as the area you create the database in is the area you use it if that makes sense?

An example is

A Ferrari is made in a factory, but you wouldn't drive it round there. You'd want to take it somewhere nice....same with Access, you make the database in Access, but I wouldn't want the database to run in Access, as this is the same place where you create it and the buttons to create new forms etc. and design views are all irrelevant when running the database.

Hope that makes sense!!

Cheers :D

[Subbynet]

What does anyone use as a front end? As Access does not have an amazing interface as the area you create the database in is the area you use it if that makes sense?

An example is

A Ferrari is made in a factory, but you wouldn't drive it round there. You'd want to take it somewhere nice....same with Access, you make the database in Access, but I wouldn't want the database to run in Access, as this is the same place where you create it and the buttons to create new forms etc. and design views are all irrelevant when running the database.

Hope that makes sense!!

Cheers :D

You can create forms that don't show all that stuff... More like a normal application.

[sm1]

Cheers Martin, but you still have all the toolbars at the top etc. that show all table options etc. ... that's what I don't like about access, it doesn't feel like a stand-alone database.

Cheers

[Subbynet]

Cheers Martin, but you still have all the toolbars at the top etc. that show all table options etc. ... that's what I don't like about access, it doesn't feel like a stand-alone database.

Cheers

Thats what I mean, you can hide that and so its kind of stand-alone. If you want it truely stand-alone, you need a developer kit from Microsoft.

[brownie]

We use Access for most of our backend.


Just to clarify, when I refer to a "website backend" I'm referring to scenario 2 above, an Access DB being accessed directly from a website.

Your setup follows scenario 1 above and is a good design.

[sm1]

Ah cheers Martin, I understand

[Steve2507]

What does anyone use as a front end? As Access does not have an amazing interface as the area you create the database in is the area you use it if that makes sense?

An example is

A Ferrari is made in a factory, but you wouldn't drive it round there. You'd want to take it somewhere nice....same with Access, you make the database in Access, but I wouldn't want the database to run in Access, as this is the same place where you create it and the buttons to create new forms etc. and design views are all irrelevant when running the database.

Hope that makes sense!!

Cheers :DWe have a number of forms which we use to enter the data. They've all been built in house so we can change them as needed.

[sm1]

Cheers Steve :D