SQL front ends

AlNipper49

Huge Member
Dope
Apr 3, 2001
41,921
Mtigawi
So I’m a geek but programming definitely isn’t my thing. I have a ton of clients with Access databases…who should not be using Access. That much I know.

Given that it’s reasonably easy to move to SQL from Access what do folks then recommend for a front end? It seems that it goes from things like SAP to ‘move it to SQL and find a developer to build you a front end’. Is there a middle ground between a grass roots development effort and something perhaps a bit more enterprise grade?
 

EddieYost

has a special friend in GHoff
SoSH Member
Jul 15, 2005
9,316
NH
What about transitioning in steps? Use Access as the front end and SQL for the backend.
 

ninjacornelius

Member
SoSH Member
Aug 18, 2005
561
Austin, TX
Every SQL front-end I've ever worked on has been built internally, but I've played around with Oracle APEX a bit in my free time and it seems to be the choice for people who need "Access Plus."
 

AlNipper49

Huge Member
Dope
Apr 3, 2001
41,921
Mtigawi
What about transitioning in steps? Use Access as the front end and SQL for the backend.
That’s actually what I have a few doing right now. Figuring that atleast with the ‘correct’ back end in place we can deal with the front end later. The main issue this is causing is that Access isn’t necessarily scalable and it’s getting really difficult to find folks to develop using it. A few of my clients have the traditional 10 year old system that has so many band aids and lost knowledge about how/why things were done that it may be better to recommend starting fresh, and I’m not sure (but not positive) that starting fresh in Access is the best move
 

voidfunkt

Member
SoSH Member
Apr 14, 2006
754
/dev/null
Every SQL front-end I've ever worked on has been built internally, but I've played around with Oracle APEX a bit in my free time and it seems to be the choice for people who need "Access Plus."
I'd have a hard time recommending any Oracle product to small businesses ever... their licensing terms and army of lawyers are sharks and bullies and they do a lot of stuff to make it difficult to know when you're in or out of compliance with the terms of your license.
 

McDrew

Set Adrift on Memory Bliss
SoSH Member
Apr 11, 2006
3,719
Portland, OR
What about transitioning in steps? Use Access as the front end and SQL for the backend.
Its this or you dip into .NET development for web or desktop. Are you doing any complicated entity management or just data entry/aggregation?
 

Max Power

thai good. you like shirt?
SoSH Member
Jul 20, 2005
5,506
Boston, MA
If you want to move completely to the cloud, Office 365 PowerApps makes it really easy to put together app front ends for your databases. SQL is a premium data source, so you have to pay $5 per month per user (after the upcoming price decrease) for it. SharePoint list data sources are free.