Gasman
Enthusiastic Amateur
- Local time
- Today, 22:07
- Joined
- Sep 21, 2011
- Messages
- 17,406
Someone resurrected a 2 year old thread?
New to Microsoft Access world, should I invest the time learning it from scratch or go for the C#, SQL Server, and ASP path? Please advice (1 Viewer)
- Thread starter hamaray
- Start date
xavier.batlle
Active member
- Local time
- Today, 23:07
- Joined
- Sep 1, 2023
- Messages
- 169
After two years of the OP, I would like to know what happened with the project!
@hamaray you're a surveyor aren't you; running cost to completes/ variation orders... I am an Estimator, gone down the path you are about to go down; 1 year further on. Working on my project full-time after quitting my job; averaging around 11 hours a day on the project every single day near enough.
I would consider myself an heavy Excel user prior to attempting the project of building my Access application. Had built & hosted 4 websites for my own construction business prior, in HTML, CSS & a tiny bit of PHP. Had taken beginner classes in C, C++, C# (several weeks per class). Was well familiar with most coding tools available; variable, loops, encapsulation, polymorphism, inheritance...
Here I am 1-year later, close to completing my project (thanks to the input from this forum; many members; particularly @MajP been very generous with his time). If I'm correct & you are a surveyor forget going the commercial language route with the other languages. It's tough enough in Access. You're project will be challenging as a lot of the time you won't find many examples relating to Construction with Access. It's mostly payroll/ invoicing...
It all seems easy until you try to do it. You find better ways of doing things as you go. You become addicted & all logic goes out of the window. IMHO stick to Access, with the possibility of linking MSSQL for the back-end or something like that. That will be great. Other users on this thread are far more capable to advise than me. But it will be a challenging project because you will have many facets to consider.
_______________________________________________________________________________________________________________
@GPGeorge relating to another thread - another bad experience with Azure.
I would consider myself an heavy Excel user prior to attempting the project of building my Access application. Had built & hosted 4 websites for my own construction business prior, in HTML, CSS & a tiny bit of PHP. Had taken beginner classes in C, C++, C# (several weeks per class). Was well familiar with most coding tools available; variable, loops, encapsulation, polymorphism, inheritance...
Here I am 1-year later, close to completing my project (thanks to the input from this forum; many members; particularly @MajP been very generous with his time). If I'm correct & you are a surveyor forget going the commercial language route with the other languages. It's tough enough in Access. You're project will be challenging as a lot of the time you won't find many examples relating to Construction with Access. It's mostly payroll/ invoicing...
It all seems easy until you try to do it. You find better ways of doing things as you go. You become addicted & all logic goes out of the window. IMHO stick to Access, with the possibility of linking MSSQL for the back-end or something like that. That will be great. Other users on this thread are far more capable to advise than me. But it will be a challenging project because you will have many facets to consider.
_______________________________________________________________________________________________________________
@GPGeorge relating to another thread - another bad experience with Azure.
Similar threads
