New Desktop Database
-
I call it a desktop database.
Paradox and Access are the two I think of.
We are a MS shop, so perhaps Access?
-
Access or FileMaker I guess. Why do this on a desktop? It's for just a single user?
-
@scottalanmiller said:
Access or FileMaker I guess. Why do this on a desktop? It's for just a single user?
Yes. Doesn't have to be on a desktop. Talk to me.
-
Well if I was needing a database, I'd always go to an enterprise one, like MariaDB, PostgreSQL, etc. Free and really powerful. With some PHP, Python or Ruby you can have a more powerful solution and one that does so much more - like isn't tied to a physical desktop, isn't tied to an OS, etc.
-
I just need something simple, which is why I was thinking Access, maybe.
-
@BRRABill said:
I just need something simple, which is why I was thinking Access, maybe.
Should be able to covert from Paradox to an Access/SQL setup:
https://www.spectralcore.com/fullconvert/howto/paradox-to-sql
Biggest thing is setting up the user experience. Using Access run time would help a lot.
-
This is all mostly for me, as I do all the DB work.
And again, when I say DB, I mean getting a mailing list in and doing various things to it. matching it to another table of separate data. Certainly not running Amazon, LOL.
-
Meh, then stick with what you got. Yeah, its more sexy to do it under any other SQL database, but if the end user experience is taken out of the equation, then f[moderated] it.
I've had to convert from a Lotus Notes DB to a SQL instance, so yeah, f[moderated] the users.
-
@PSX_Defector said:
Meh, then stick with what you got.
My problem is that all of a sudden Paradox is freezing up on me all the time. I think it happened when I moved from 4GB to 8GB. The program is like 20 years old, so I think that's the issue.
There used to be a great online forum, but it seems to have died.
http://www.thedbcommunity.com/ ---- DEAD
-
If there was a SQL DB as easy ac Access (looks), I'd be up for that.
-
@BRRABill said:
If there was a SQL DB as easy ac Access (looks), I'd be up for that.
Convert it to SQL Express running on your desktop.
Connect Access to SQL Express.
-
@JaredBusch said:
Convert it to SQL Express running on your desktop.
Connect Access to SQL Express.
For simple DBs why not just leave it in Access?
-
Actually I guess I should go about this another way, or pose the question another way.
I am used to a simple desktop GUI database. Simple clicks to run queries, mail merges, etc..
But moving forward I will need to relearn whatever program I am using, whether it be Access on a SQL product.
So, if you were going to recommend an easy to use, easy to figure out DB program, what would it be?
All of my data is lcoal, on our network.
-
Side Question:
Is Access available through Office 365? -
I hate Access with a passion. I will never recommend it.
-
@BRRABill said:
Side Question:
Is Access available through Office 365?Yes, any time that you get MS Office via one of the E plans, Access is included.
-
@BRRABill said:
@JaredBusch said:
Convert it to SQL Express running on your desktop.
Connect Access to SQL Express.
For simple DBs why not just leave it in Access?
Because Microsoft Access is a horrible database program. . . MySQL or MariaDB are way better options.
-
I'd use LebreBase over Microsoft Access. . .
-
@BRRABill said:
For simple DBs why not just leave it in Access?
Let's reverse that.... why would you ever not take the tiny effort to not do something good? Why set yourself up for problems when you can avoid them? Why would you choose the bad option when good options are freely available?
Access is...
- Not a serious database by any measure and not meant to be used for anything beyond learning and demos.
- Not taken seriously by IT pros and there is essentially no one knowledgeable or willing to be knowledgeable on it.
- Not an RDBMS and therefore not designed around multi-user access.
- Not free, which anything in this range should be. Enterprise options are free, why would you opt for less?
- Tied to not being free, updates are not free. You pay today, you pay forever.
- Not portable. Access only runs on Windows, highly impractical for a database of all things.
- Not scalable. If you need to go big, you can't.
- Not fast. If you want speed, you don't get it.
- Highly subject to corruption. That's not a problem that a database should have.
- Not web based from the application side, this should rule it out right there.
- Not designed to run from a server, this again should just rule it out as a non-starter.
- Not designed to be backed up reliably. This should rule it out, right there.
-
@BRRABill said:
But moving forward I will need to relearn whatever program I am using, whether it be Access on a SQL product.
This is a key here. You are already taking the time to relearn something. Relearn something useful. Don't invest in useless technical debt.
