|
An .mdb file is compatible with Access 2002/2003/2007/2010 - I only use .mdb files.
If it's breaking it's probably a conversion issue, not compatibility. Instead of converting, try copying and pasting the data. Or, upload the data to SQL Server (Express) and then use a make-table query to bring it back to a newly created Access .mdb file.
|
|
|
|
|
Access is a database system - and yes, it's still used. Should you? Probably not.
It's not a bad DB system, and for a single user it works fine, the management system isn't bad, and it's easy to work with from your code.
But...as soon as you move to a multi user environment, it all turns to poo.
Personally, I paid for it as part of Office, but I don't use it - I use SQL Server instead, even for "private" single user (i.e. me) applications. Internally, it uses the same files as Access, but it wraps it in a layer of comforting security.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I remember it been used along time ago for a stores DB (not by me, I was young and DB were the preserve of the gods!!)
But if I want a DB for my app I've always used SQL Compact and lately, LocalDB.
|
|
|
|
|
I've made four highly multi-user applications with Access, three now in use at manufacturing companies. The multi-user part is a challenge. I set these up so that each user gets their own appplication file on their client PC connected to the data file on the server. I've also made an auto-updater file that automatically updates the client PC with the latest files each time the user logs in.
|
|
|
|
|
Same here.
I have an Access based application running my company for 18 years. I think it's ok up to 25 users. If we needed more users I would consider a back end based in SQL Server or Maria DB, but the front end is ok to make quick forms an reports.
Our database is 800Mb and keeps tables with way more of 100k records. Just don't keep LBOs there, try a workaround and everything will be fine.
If I started today I would choose another database engine. But then again, Access is taking care here of an aplication that involves invoicing, suply chain management, payrolls, bookkeeping, Document management, and some sophisticated functions like geolocation, web content management.. .etc
|
|
|
|
|
SPoss wrote: What for?
To upgrade all your legacy .mdb files to the latest version. Not likely, but still no one knows when MS will stop supporting Versions 200x of those.
|
|
|
|
|
Avijnata wrote: no one knows when MS will stop supporting Versions 200x of those.
The trouble is, a lot of MS Access isn't even backwards compatible. We have one database in our office that uses it and tbh I can't wait to find time to replace it.
|
|
|
|
|
My dad uses it.
He worked for many years as a VAT Inspector before becoming an internal auditor for Customs & Excise. This made him a very boring man.
He has a number of Access DBs he has created on his laptop to store his stuff on.
It is perfect for that.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
This is exactly what the current value of Access is. And it's a very good value!
|
|
|
|
|
I use it only for personal-use databases.
For a production database, or if the number of expected users exceeds 1, I would rather avoid Access' usage.
while (true) {
continue;
}
|
|
|
|
|
Hi, my Name's Guy and I used to be an Access developer.
I used to write applications with Access(Years ago) - most of them were coding horrors.
I would recommend avoiding it.
It presents itself as a quick way top write database based applications without needing to know about good database or good application design.
Sure it looks nice to end-users and persuades them that they can code and create databases - however the chimera of monstrosities that have been birthed by Access would make even Cerberus throw up his dinner and I understand that if there was a modern day Sisyphus, his task would be to fix Access databases and Access applications.
What starts off as a quick and easy application gets added to and after a few years data a business relies on is embedded in a system that hides functionality and makes tracing issues difficult.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
modified 3-Oct-15 4:12am.
|
|
|
|
|
The problem with Access isn't as much Access itself, but rather its intended audience.
|
|
|
|
|
That's nicely put!
|
|
|
|
|
Does anyone use it? Yes.
Are there valid reasons to use it? Yes, with caveats.
I have heard of it being used by individuals working for charitable organizations when the individual is essentially cut off from field support, ie: they are on their own. Think interval Africa.. really, used by people in Africa without access to the internet for support.
I have seen it used (badly) in a commercial organization by the accounting group because 'someone' thought they knew how to create a database and the attendant code and couldn't be bothered asking the IT department for help.. that would take to long. So, when the database grew to over 5G and couldn't be shrunk and was tied to a particular machine that couldn't be re-imaged, etc... they refused to admit they had erred years before, but reluctantly asked the IT department for help is moving the functionality to SQL Server.
|
|
|
|
|
I was going to say, why don't they use locaDB/sqlexpress instead, but thinking about it, if your in Africa etc, and you're an end user (not a developer), and you have need for a DB, what options do you have? I had a very quick look at access this morning, it does seem to come with ready made templates that an end user could quickly get setup and use.
I'm not about to start using it!! 
But for non developer/end users that want a simple DB, what other options do they have? Search for an app already made for the job. As an example, I've just googled 'CD Database software' ... and there where lots of hits
|
|
|
|
|
You can easily connect an Access app file to SQL Server (or Express).
Keep searching for template files - MS has made many available!
|
|
|
|
|
I have a difficult time imagining that a developer has no idea what Access is. Perhaps I missed the sarcasm? Since you already have it installed, I'd suggest that you try it and decide for yourself if it might be useful to you...it won't cost you a thing.
That said, I use Access 2003 almost every day. Why? Two words: Query Designer
"Go forth into the source" - Neal Morse
|
|
|
|
|
No Sarcasm, genuine question. I've been aware of Access since windows 3.1 (I think access was available then, anyway along time), just never used it. Just never though/considered it's use, no reason not to.
During my early programming life, it was all embedded microcontrollers running C/asm with about 32K of program code. My most of the work is still embedded stuff.
I've only really started using DB in the last 6 years. combination of sql compact, express, localDb and MySQL, selecting whichever suited the project/client the best. I'm no DB expert, there's always something to learn!!
But I updated office yesterday, noticed access and opened it up to have a look. Which made me wonder if any one currently uses it.
|
|
|
|
|
|
Query designer in Access is also my fallback tool when I'm having trouble figuring out how to write a SQL string in code! 
|
|
|
|
|
ACCESS is so good that MS is killing it because is a big competitor of VS. ACCESS is the fastest RAD tool and you can do petty good desktop and web applications for SME or departments almost without code. Access it is simply fantastic. And of course there are millions of people using ACCESS.
|
|
|
|
|
MS stopped making improvements in Access with the 2003 version. But - they have improved Access for power users since then.
It doesn't make sense for MS to put resources into improving two products for the same set of developers. The IDE in VS is much better than the IDE in Access.
|
|
|
|
|
Access is great for manipulating data from one format to another, outside of that I have not used it
|
|
|
|
|
I also used MSAccess for back-end DB while ago..
But now I'm using LocalDB or sometimes SQLite... 
Don't watch the clock;
Do what it does.
Keep going.....
|
|
|
|
|
Many years ago but I don't want to see it again - ever.
However, I'd gladly go with dBase III and Clipper again.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
Anyway, have a great weekend!