Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Hello, What is the best platform
- Thread starter Akart
- Start date
- Thread starter
- #3
Thanks for your reply.
Have you used Access, vb.net and c# ?
Is it hard to go from Access to c#?
Can you tell me a couple of reasons why the latter is better?
Sorry to hound you with all these questions, I just want to make the right choice from the beginning.
Regards,
Akart
Have you used Access, vb.net and c# ?
Is it hard to go from Access to c#?
Can you tell me a couple of reasons why the latter is better?
Sorry to hound you with all these questions, I just want to make the right choice from the beginning.
Regards,
Akart
The single biggest problem with Access is that it is designed for samll databases. Once databases get large they have to be upsized to a different relational database such as SQL Server or Oracle or even MYSQL. Inherent in this upgrade are the inevitable problems of transitioning from one product to another, particularly as the same SQL code which works for Access does not necessarlity work for a differnt database.
Access has a nice user interface and it is quick to develop in, but it lacks the power of Visual Basic or C++ or Visual Studio.Net. Again fine for simple samll application , bad for large data or complex enterprise type organizations. If you will be doing web development it is best, I think, to use the tools that were designed for web development, not Access which had some limited functionality grafted on.
Web databases in particular have to be planned for possible hugh growth because their data entry tends to pull from a much large user base than a small internal application. And they run 24-hours a day which can make maintenance a real issue. Plus the users can have a slow connection which exacerbates the inherently slower speed of Access.
More and more we find our customers only want web-based development done, even for those things which in the past would have been small internal applications. Therefore it makes the most sense to use the tools that were designed specifically for this environment. We like .Net with a SQL Server backend because we are a Microsoft shop; all our servers are Windows servers. If we were in a Unix environment we would probably use a different database and J2EE. People also use Cold Fusion and Java and ASP for their web front end and a wide variety of databases for the backend, but more and more people seem to be moving away from the Access environment.
Are the new environments hard for an Access programmer to pick up. Yes, they have a high learning curve because there are many new issues to consider that were not important or even options in Access. Also, many Access programmers have had no formal programming training and some only create applications using the wizards and are not even slightlly familiar with vba or SQL code. THe more you used vba and sql, the better concepts you will have for moving to a different environment, but it is still a difficult process which will take time and effort on your part to learn. Is it worth making the change? I did it 1.5 years ago and I would never go back to Access. The projects I handle now are much more interesting and the salary I can command is higher.
Access has a nice user interface and it is quick to develop in, but it lacks the power of Visual Basic or C++ or Visual Studio.Net. Again fine for simple samll application , bad for large data or complex enterprise type organizations. If you will be doing web development it is best, I think, to use the tools that were designed for web development, not Access which had some limited functionality grafted on.
Web databases in particular have to be planned for possible hugh growth because their data entry tends to pull from a much large user base than a small internal application. And they run 24-hours a day which can make maintenance a real issue. Plus the users can have a slow connection which exacerbates the inherently slower speed of Access.
More and more we find our customers only want web-based development done, even for those things which in the past would have been small internal applications. Therefore it makes the most sense to use the tools that were designed specifically for this environment. We like .Net with a SQL Server backend because we are a Microsoft shop; all our servers are Windows servers. If we were in a Unix environment we would probably use a different database and J2EE. People also use Cold Fusion and Java and ASP for their web front end and a wide variety of databases for the backend, but more and more people seem to be moving away from the Access environment.
Are the new environments hard for an Access programmer to pick up. Yes, they have a high learning curve because there are many new issues to consider that were not important or even options in Access. Also, many Access programmers have had no formal programming training and some only create applications using the wizards and are not even slightlly familiar with vba or SQL code. THe more you used vba and sql, the better concepts you will have for moving to a different environment, but it is still a difficult process which will take time and effort on your part to learn. Is it worth making the change? I did it 1.5 years ago and I would never go back to Access. The projects I handle now are much more interesting and the salary I can command is higher.
- Thread starter
- #5
Thanks for taking the time to answer me.
I will most likely lose Access now. There seems to be a trend of people moving from access to other MS products and i was considering moving from filemaker to access due to database growth. That may have been a big mistake.
Luckily i have only been creating an Access database for 3 weeks
mainly learning VBA which will probably have similarities to VB.net.
Akart
I will most likely lose Access now. There seems to be a trend of people moving from access to other MS products and i was considering moving from filemaker to access due to database growth. That may have been a big mistake.
Luckily i have only been creating an Access database for 3 weeks
mainly learning VBA which will probably have similarities to VB.net.Akart
tlbroadbent
MIS
Akart,
If you have Access 2000 or higher, you can use MSDE as the database engine. MSDE is the desktop version of SQL Server and it is provided with Access. You can use Access as the front-end to MSDE or you can use the other software products mentioned.
I recommend checking into MSDE on the Microsoft Web site or Access help. Here are a few links to get upi started.
Terry L. Broadbent - DBA
SQL Server Page:
If you want to get the best answer for your question read faq183-874.
If you have Access 2000 or higher, you can use MSDE as the database engine. MSDE is the desktop version of SQL Server and it is provided with Access. You can use Access as the front-end to MSDE or you can use the other software products mentioned.
I recommend checking into MSDE on the Microsoft Web site or Access help. Here are a few links to get upi started.
Terry L. Broadbent - DBA
SQL Server Page:
If you want to get the best answer for your question read faq183-874.
- Thread starter
- #7
Thanks,
However i have the access developer version which i have been developing an access project on.
This uses access as a front-end and sql server as a back-end.
I wanted to know which was better, access with sql server ot visual basic.net/c#.net etc with sql server.
Akart
However i have the access developer version which i have been developing an access project on.
This uses access as a front-end and sql server as a back-end.
I wanted to know which was better, access with sql server ot visual basic.net/c#.net etc with sql server.
Akart
- Status
Similar threads
- Locked
- Question
- Locked
- Question