When you think that the changes are required for an Ms Access Developer to go for an SQL Server Localdb along with accdb files. (side-by-side). Going to localdb only for non-available features in Access.

Note:
I know that many experts over here doesn't feel Ms Access as a Good Database System. But I am an Ms Access Database Developer primarily. It's a Good File based DB for RAD (Rapid Application Development)

 

When you think that the changes are required for an Ms Access Developer to go for an SQL Server

When your potential customers require SQL.

 

When you think that the changes are required for an Ms Access Developer to go for an SQL Server Localdb along with accdb files. (side-by-side). Going to localdb only for non-available features in Access.

Note:
I know that many experts over here doesn't feel Ms Access as a Good Database System. But I am an Ms Access Database Developer primarily. It's a Good File based DB for RAD (Rapid Application Development)

It's a joke, MS Access was useful in some cases years ago, but it's a poor choice today when we have Azure and AWS.

Put the DB in the cloud along with your code and websites and say bye bye to all the files, backups, etc. You can host customers sites yourself in Azure and charge them a subscription, use that to pay your own subscription and keep the profits.

No machines, no OS updates, no fiddling around.

 

I suppose it depends on what you want the database to do. I'm not an expert but I did use MS Access in an intro computer science course. It seemed outdated and I prefer to use free, open-source software. Like most programming languages, once you understand a few, you can understand them all and SQL is the same idea. As for the purpose, I separate databases into three general categories:

1) Simple Databases - I didn't get into the advanced features of MS Access as it's not really relevant to my interests. That being said, it seemed like a program meant for general employees and low level technicians. It has a nice GUI and made it easy to create tables and relate them with keys. All things considered, MS Access did what I wanted and I got full marks on the assignment I used it for.

2) Self-managed Databases - I use Linux, Apache, MySQL, PHP (LAMP) stacks to manage my databases. I've sampled a few other types but prefer these specifically because of extensive documentation and robust security. The syntax of MySQL is very similar to MS Access hence the acronym SQL. Once you have a grip on SQL, you can manipulate the database using a variety of back-end languages. Major downsides are SQL injection attacks and memory issues.

If you are interested, I can give you access to one of my servers. I'm working on a project for my YouTube channel where I show how to build a forum similar to AllAboutCircuits entirely from scratch. I programmed the HTML, CSS, Javascript, PHP, MySQL as well as the Apache back-end. The database itself is broken into two parts, first I instantiate the database using raw SQL with Linux bash. Once the tables and keys are created, PHP is used to read and enter the specific entries. This setup may seem complicated but it's more of a bunch of little things that need to be set up correctly.

3) Partially-managed Databases - Examples include Azure and AWS. Lots of advanced features and good security. Obviously since you are using their hardware and resource, you'll pay for it in the long run. Also have to learn to use their specific syntax which is unique to each provider.

An excellent option is cloudflare.com. They have a free tier with a ton of value for individual developers. Besides databases, they offer "Pages" and "Workers". Pages are static HTML/CSS/Javascript and Workers are back-end Javascript / Python. All together you can get a fully functional database online within minutes. I highly recommend Cloudflare even if you don't run a website.

One thing I use Cloudflare for is to generate images with AI. I use one worker to generate the prompt which is stored in a database. Then another worker gets the prompt from the database and uses it to generate an image. Very cool stuff and it's all free.

 

I suppose it depends on what you want the database to do. I'm not an expert but I did use MS Access in an intro computer science course. It seemed outdated and I prefer to use free, open-source software. Like most programming languages, once you understand a few, you can understand them all and SQL is the same idea. As for the purpose, I separate databases into three general categories:

1) Simple Databases - I didn't get into the advanced features of MS Access as it's not really relevant to my interests. That being said, it seemed like a program meant for general employees and low level technicians. It has a nice GUI and made it easy to create tables and relate them with keys. All things considered, MS Access did what I wanted and I got full marks on the assignment I used it for.

2) Self-managed Databases - I use Linux, Apache, MySQL, PHP (LAMP) stacks to manage my databases. I've sampled a few other types but prefer these specifically because of extensive documentation and robust security. The syntax of MySQL is very similar to MS Access hence the acronym SQL. Once you have a grip on SQL, you can manipulate the database using a variety of back-end languages. Major downsides are SQL injection attacks and memory issues.

If you are interested, I can give you access to one of my servers. I'm working on a project for my YouTube channel where I show how to build a forum similar to AllAboutCircuits entirely from scratch. I programmed the HTML, CSS, Javascript, PHP, MySQL as well as the Apache back-end. The database itself is broken into two parts, first I instantiate the database using raw SQL with Linux bash. Once the tables and keys are created, PHP is used to read and enter the specific entries. This setup may seem complicated but it's more of a bunch of little things that need to be set up correctly.

3) Partially-managed Databases - Examples include Azure and AWS. Lots of advanced features and good security. Obviously since you are using their hardware and resource, you'll pay for it in the long run. Also have to learn to use their specific syntax which is unique to each provider.

An excellent option is cloudflare.com. They have a free tier with a ton of value for individual developers. Besides databases, they offer "Pages" and "Workers". Pages are static HTML/CSS/Javascript and Workers are back-end Javascript / Python. All together you can get a fully functional database online within minutes. I highly recommend Cloudflare even if you don't run a website.

One thing I use Cloudflare for is to generate images with AI. I use one worker to generate the prompt which is stored in a database. Then another worker gets the prompt from the database and uses it to generate an image. Very cool stuff and it's all free.

Have you looked at Visual Studio? If not you'll be blown away at how straightforward it is to create a website with authentication, databases and more.

Literally you start a new project pick a template and that's it.

No Javascript needed, no Python needed. Back and front end can all be coded in C# just one language. Publishing the site is trivial too.

 

Have you looked at Visual Studio? If not you'll be blown away at how straightforward it is to create a website with authentication, databases and more.

Literally you start a new project pick a template and that's it.

No Javascript needed, no Python needed. Back and front end can all be coded in C# just one language. Publishing the site is trivial too.

I am trying to switch myself from VB.Net to C# for almost an year but still haven't grasped it well...

 

I am trying to switch myself from VB.Net to C# for almost an year but still haven't grasped it well...

Well VB.Net is very similar functionality but very different syntactically. They both operate within the .Net runtime, create objects and so on.

C# is a very good language to build business functionality, once you're underway the productivity is huge.

Use copilot if you have questions.

 

Well VB.Net is very similar functionality but very different syntactically. They both operate within the .Net runtime, create objects and so on.

C# is a very good language to build business functionality, once you're underway the productivity is huge.

Use copilot if you have questions.

I agree. I heard Microsoft is goanna kill VB soon. Until that last drop of vb.net I dedicate myself to the language which made grow as an amateur to a professional... VB.. VB.. VB... (my pulse readings)

 

Just for joke. Don't take it very seriously. Microsoft will definitely pave a way for a smooth transition from VB to C# soon...

 

Just for joke. Don't take it very seriously. Microsoft will definitely pave a way for a smooth transition from VB to C# soon...

Just get a decent book and start learning or look at Youtube for helpful videos.

https://www.vishalon.net/blog/convert-vb-net-to-csharp

Also do use Copilot, if you ask stuff like "In VB I can do this XXXX how is that represented in C#?" you'll get very good answers.

 

"VB!","VB!","VB!"

 

"VB!","VB!","VB!"

 

Have you looked at Visual Studio? If not you'll be blown away at how straightforward it is to create a website with authentication, databases and more.

Literally you start a new project pick a template and that's it.

No Javascript needed, no Python needed. Back and front end can all be coded in C# just one language. Publishing the site is trivial too.

I'll check it out but I prefer full control over the entire back-end and use many languages. I'm also morally against Microsoft.

What kind of projects have you used it for?

 

I'll check it out but I prefer full control over the entire back-end and use many languages. I'm also morally against Microsoft.

What kind of projects have you used it for?

I simply cannot comment or react to "moral" based decisions, these are relevant sometimes but not in the objective way we are discussing engineering.

If you refuse to use Microsoft technologies then that's fine but there's no point trying to discuss the matter technically.

Now technically MS have gradually embraced open source and done it well, the entire .Net Core (as it was once named) is designed to be OS and platform agnostic. So .Net Core runs fine on Linux, iOS, Mac, Windows and on ARM x86/x64 and RISC-V.

So today I can write a complex web service and it will run on Linux or Windows as-is.

I can write a GUI app that runs on iOS, Android or Mac, tablet or phone - in C#.

MS have produced Blazor and Web Assembly. A Blazor website uses a high speed async channel back to the server (hidden from the developer) which allows server side code to react to UI events like mouse clicks, scrolls, etc.

So UI code runs on the server but we code it as if it ran locally, the abstraction is very powerful and they have done an excellent job with this.

This mean you don't really need JS at all for the front end. Under the hood the "Blazor components" might use JS (even a lot) but that is encapsulated and the exposed interface is pure .Net).

If you want to use JS you can, but with Blazor it has become akin to assembler, some bits in pieces can be coded that way but they don't dictate the overall paradigm.

I love programming languages (Ive built them) but on serious projects the less languages you have and the fewer friction points the better.

Finally VS community edition is free, arguably the best IDE available from anybody anywhere, so forget Eclipse, Java and all the other clunky idiosyncratic outdated junk.

As a web developer, you'll like this

 

I simply cannot comment or react to "moral" based decisions, these are relevant sometimes but not in the objective way we are discussing engineering.

If you refuse to use Microsoft technologies then that's fine but there's no point trying to discuss the matter technically.

Now technically MS have gradually embraced open source and done it well, the entire .Net Core (as it was once named) is designed to be OS and platform agnostic. So .Net Core runs fine on Linux, iOS, Mac, Windows and on ARM x86/x64 and RISC-V.

So today I can write a complex web service and it will run on Linux or Windows as-is.

I can write a GUI app that runs on iOS, Android or Mac, tablet or phone - in C#.

MS have produced Blazor and Web Assembly. A Blazor website uses a high speed async channel back to the server (hidden from the developer) which allows server side code to react to UI events like mouse clicks, scrolls, etc.

So UI code runs on the server but we code it as if it ran locally, the abstraction is very powerful and they have done an excellent job with this.

This mean you don't really need JS at all for the front end. Under the hood the "Blazor components" might use JS (even a lot) but that is encapsulated and the exposed interface is pure .Net).

If you want to use JS you can, but with Blazor it has become akin to assembler, some bits in pieces can be coded that way but they don't dictate the overall paradigm.

I love programming languages (Ive built them) but on serious projects the less languages you have and the fewer friction points the better.

Finally VS community edition is free, arguably the best IDE available from anybody anywhere, so forget Eclipse, Java and all the other clunky idiosyncratic outdated junk.

As a web developer, you'll like this

Nice review. The comment about morality was more of a joke, I know Microsoft puts outs a lot of high quality enterprise software that will be in use for many years.

I'm gonna try C# for Android. Blazer also looks handy. Maybe you can give me a hand with a simple GUI for BLE device.

 

The key appeal of Blazor is they designed it rationally. The entire approach is just what a true engineer would take.

You can also create a pure GUI app (MAUI) on these platforms too or combine MAUI with Blazor, there's never been so much potential to create sophisticated apps on all these platforms from a single code base.



Say farewell to Java.