- Joined
- Jul 6, 2005
- Messages
- 7,235
- Likes received
- 209
- Thanks received
- 41
- Location
- whereever the work is
Ofthe the reason is down to Access being included in Office Pro rather than Office Std and so does not tend to get deployed as often. Also there tends to be fewer people kicking about who can make a database than can throw together a spreadsheet. I've worked at loads of places where they have struggled to implement database functionality into a spreadsheet but simply will not accept a database! On the plus side it gives ample opportunity to keep on generating invoices! Grin and bank it!
it is possible to do and not difficult. I also would side with the Access solution as things can become a mess in Excel very easily!
A spreadsheet. Sheesh.
Wrong tools.
A spreadsheet. Sheesh.
Wrong tools.
I used Access many years ago to keep software licence details for a fleet of systems.
When I tried to open the database a few years later, Access claimed it couldn't read that version.
I was not impressed. At all.
Even if I hadn't come across that little gem, the new PC that arrived a little later didn't have Access.
Fortunately I still had the scripts I'd written to grab that data again, and shove it into a proper database (Oracle).
I have recommended SharePoint, as it is quite easy to do most of what I want using the workflows built in.