Access going away?

[NauticalGent]

which has a steep learning curve and significantly longer development times.

Exactly, which is why I said what I did about Home Depot...I'm not as savvy as most of you and it would be even steeper for the likes of me.

 

[CedarTree]

In response - I don't like the fact that if you want your application to have nice animations, top security, web deployment, fancy styling, control customization, mobile versions, etc... you're on your own and you end up choosing another platform which has a steep learning curve and significantly longer development times.

Not sure I'm following this item...

 

[AccessBlaster]

Thanks everyone - great insight.
If you HAD to give up Access tomorrow... what would you go to. that you think IT would support? Visual Studio? Something else?

A web page interface with SQL tables, possibly .NET Our IT department had a .NET developer who offered to convert my builds. I retired before we could start testing.

 

[Isaac]

In response - I don't like the fact that if you want your application to have nice animations, top security, web deployment, fancy styling, control customization, mobile versions, etc... you're on your own and you end up choosing another platform which has a steep learning curve and significantly longer development times.

That's a reasonable come back -
After all, if you want the top-tier most advanced level features, shouldn't you expect the most top-tier, advanced level of time and knowledge.

 

[Isaac]

Thanks everyone - great insight.
If you HAD to give up Access tomorrow... what would you go to. that you think IT would support? Visual Studio? Something else?

If Access went away forever tomorrow, and IF I got back into the world of FE design, I would absolutely unequivocally take the time (probably some classes at a local tech school, as this IMO is way too sophisticated to learn only OJT and by forums - and I would dignify it by recognizing this)................ to learn to make simple Winform applications in visual studio using c#.net.

I have seen this done several times by guys at my companies and it seems like a pretty good, standard way to go where you end up mainstream - with a mainstream application, a trusted & respected platform, and essentially all the desktop-app-options that you need.

It would also give me a chance to say 'bye-bye' to all things Visual Basic and force myself if I am going to take the time to learn .net, to choose c# over vb, which I think would be good for me.

Note - in all of this I assumed you did not need mobile or web, just a good desktop replacement for Access.

Edit - In fact, this reminds me I really want to learn to do this anyway! Maybe I will devote 15 hours a week to this instead of looking for that part time remote SQL job I have been looking for!

 

[561414]

In response - I don't like the fact that if you want your application to have nice animations, top security, web deployment, fancy styling, control customization, mobile versions, etc... you're on your own and you end up choosing another platform which has a steep learning curve and significantly longer development times.

In response - which has a steep learning curve and significantly longer development times in the beginning, like everything (and, like everything, that depends on your strategy, take xaml in .NET as an example, or web component libraries, or DESIGN PATTERNS like MVC, which let you reuse and organize your workflow better). Sadly, I'm yet to hear a client tell me "And I need that in Access", it usually is me who recommends it when they want something quick. You are preaching to the choir, I would love to be able to simply export a .accdb to the web, the place my people want their stuff most of the time.

 

[Amicron]

If I had a nickel every time someone asked me this, I'd have... Probably enough for a steak dinner. Not at a high class steak house... Maybe like Outback... But yeah... Probably once a week. I get asked this so much, in fact, I made a video about it. I'd post a link to it, but your forum won't let me. Just Google "access going away 599cd" and you'll find it.

Richard Rost
Access Learning Zone

 

[NauticalGent]

Welcome to AWF Richard Rost, I have learned a thing or two from your site...

 

[Amicron]

Thanks.

 

[561414]

@Amicron Richard Rost, thank you for your work. I learned a ton from you, your teaching method is pure gold.

 

[Amicron]

Thank you very much

 

[isladogs]

Richard
The links ban is designed to hinder spammers and only applies to new members.
If you post here as often as you release new videos on your site, you'll be able to post links within a few days.
I'm very impressed not just by the quality of your videos but also by the frequency you release them.
Don't know how you find the time. I manage less than one new video a week on my channel

 

[gemma-the-husky]

I've thought a time or three about converting some Access databases to a "proper" language, but

a) it's a big learning curve learning a new language.
b) it just doesn't seem so easy to bind a form to data and have an immediately interactive form in the way we can do with Access.
c) the database I would really like to convert is extremely large.

I don't know if I'm missing something, but it just doesn't seem particularly easy.


.

 

[GPGeorge]

In response - which has a steep learning curve and significantly longer development times in the beginning, like everything (and, like everything, that depends on your strategy, take xaml in .NET as an example, or web component libraries, or DESIGN PATTERNS like MVC, which let you reuse and organize your workflow better). Sadly, I'm yet to hear a client tell me "And I need that in Access", it usually is me who recommends it when they want something quick. You are preaching to the choir, I would love to be able to simply export a .accdb to the web, the place my people want their stuff most of the time.

Check out Hybrid Applications as a way to migrate a sub-set of the functions in your Access relational database application. I gave a presentation on that approach to the AUG - Europe group on PowerApps for Access Developers. PA is one way to achieve that hybrid solution. While I lean towards the PowerApps approach because it fits well with other MS solutions, there is no reason you can't do the same thing with other web interface solutions. The point is that the entire rich Access application need not be replaced or replicated. If one function (say, for example, employee logins for shift start and end) would be more useful running on a smart phone, then only that function needs to be replicated. It also has the advantage of allowing you to get your toes wet in a new environment without incurring the burden of a full-blown development project.

 

[Amicron]

Richard
The links ban is designed to hinder spammers and only applies to new members.
If you post here as often as you release new videos on your site, you'll be able to post links within a few days.
I'm very impressed not just by the quality of your videos but also by the frequency you release them.
Don't know how you find the time. I manage less than one new video a week on my channel

It is very time consuming, but it's something I love doing, so I make the time. Thanks for the compliment.

 

[561414]

Check out Hybrid Applications as a way to migrate a sub-set of the functions in your Access relational database application. I gave a presentation on that approach to the AUG - Europe group on PowerApps for Access Developers. PA is one way to achieve that hybrid solution. While I lean towards the PowerApps approach because it fits well with other MS solutions, there is no reason you can't do the same thing with other web interface solutions. The point is that the entire rich Access application need not be replaced or replicated. If one function (say, for example, employee logins for shift start and end) would be more useful running on a smart phone, then only that function needs to be replicated. It also has the advantage of allowing you to get your toes wet in a new environment without incurring the burden of a full-blown development project.

I agree that having the options is important, thank you, George.

 

[gemma-the-husky]

I think if MS were ever to try to retire Access it would make a lot of people very unhappy. There must be untold billions of dollars invested in Access databases that need to carry on working. Just thinking out loud, I wouldn't be surprised if courts might not actually prevent MS doing that.

 

[Pat Hartman]

When someone makes a viable replacement, Access will walk slowly into the sunset. But until then, NOTHING MS has come up with has even challenged it.

 

[CJ_London]

Or anyone else

 

[tmyers]

Check out Hybrid Applications as a way to migrate a sub-set of the functions in your Access relational database application. I gave a presentation on that approach to the AUG - Europe group on PowerApps for Access Developers. PA is one way to achieve that hybrid solution. While I lean towards the PowerApps approach because it fits well with other MS solutions, there is no reason you can't do the same thing with other web interface solutions. The point is that the entire rich Access application need not be replaced or replicated. If one function (say, for example, employee logins for shift start and end) would be more useful running on a smart phone, then only that function needs to be replicated. It also has the advantage of allowing you to get your toes wet in a new environment without incurring the burden of a full-blown development project.

I have wanted to try PowerApps as I want to move more towards web based apps but my IT department has it locked for sign up and hasn't agreed to unlock my account so I can try it .