Visual Basic vs. Access
- Thread starter Rob.Mills
- Start date
Big topic. Small answer.
If written in VB, you will probably have less trouble distributing the app, but you will also probably spend more time writing the app (unless, of course, you are a seasoned VB DB programmer and not a seasoned Access Developer).
Regards,
Tim
If written in VB, you will probably have less trouble distributing the app, but you will also probably spend more time writing the app (unless, of course, you are a seasoned VB DB programmer and not a seasoned Access Developer).
Regards,
Tim
Well the reason I was asking is that a friend of mine said that I would probably have less errors happen if I designed the application totally in VB. I've never used VB so I didn't know if this was true.
Basically, I'm trying to find the best way to set it up. Using VB, Access on the frontend and backend, or Access project on front and SQL Server on back.
Basically, I'm trying to find the best way to set it up. Using VB, Access on the frontend and backend, or Access project on front and SQL Server on back.
- Local time
- Today, 18:47
- Joined
- Feb 19, 2002
- Messages
- 47,594
An Access Project with SQL server backend would limit your customer base to those who have SQL server installed unless this is a single user application. The desktop version that ships with Access is limited to FOUR users.
If you don't know how to program, you are biting off more than you can chew by attempting to do the front end with VB. The only reason to ever use a Jet backend is because you have used an Access frontend.
If you don't know how to program, you are biting off more than you can chew by attempting to do the front end with VB. The only reason to ever use a Jet backend is because you have used an Access frontend.
Hey Pat!
Was hoping this thread would catch your eye. And thanks for your input.
I had the same thoughts when it came to VB as you in that it would be too much for my little experience.
Reason I mentioned SQL server on the backend is that I read the Office developer program has a run-time version of sql server which I took to mean that you can install a full version that is only available to the package you install. Am I correct in my thinking?
But what are your thoughts on the stability of Access as a front and backend? Because what I want to do is create an entire package through developer that I can install for any company and naturally have as few problems as possible. Obviously a lot of that depends on my ability to set it up correctly. But I probably wouldn't have questioned Access if it weren't for my friend. Probably should never have seeked his advice.
Was hoping this thread would catch your eye. And thanks for your input.
I had the same thoughts when it came to VB as you in that it would be too much for my little experience.
Reason I mentioned SQL server on the backend is that I read the Office developer program has a run-time version of sql server which I took to mean that you can install a full version that is only available to the package you install. Am I correct in my thinking?
But what are your thoughts on the stability of Access as a front and backend? Because what I want to do is create an entire package through developer that I can install for any company and naturally have as few problems as possible. Obviously a lot of that depends on my ability to set it up correctly. But I probably wouldn't have questioned Access if it weren't for my friend. Probably should never have seeked his advice.
SforSoftware
(NL) SnelStart specialist
- Local time
- Tomorrow, 00:47
- Joined
- Aug 16, 2003
- Messages
- 239
Hi Rop,
The SQL-server edition that ships with Office Developer is not a run-time edition, but a developers-editions. You're only allowed to use that version for developing and testing and can not ship it to your customers.
If Access is the right choice depends of the type of application you want to build. If it is an application with manu people working (editing) in it, access kan cause problems.
To the front-end: always create an mde-file. That's the most stable type of Access-files. The size of the app. shrinks to ca. 1/3 of the mdb-file and it works better, because the code is more compiled.
Always VB is the more stable than Access, because VB compiles your written code to machine-code. Access doesn't that, so your code is 'compiled' at runtime (only in memory, not in een executable).
The SQL-server edition that ships with Office Developer is not a run-time edition, but a developers-editions. You're only allowed to use that version for developing and testing and can not ship it to your customers.
If Access is the right choice depends of the type of application you want to build. If it is an application with manu people working (editing) in it, access kan cause problems.
To the front-end: always create an mde-file. That's the most stable type of Access-files. The size of the app. shrinks to ca. 1/3 of the mdb-file and it works better, because the code is more compiled.
Always VB is the more stable than Access, because VB compiles your written code to machine-code. Access doesn't that, so your code is 'compiled' at runtime (only in memory, not in een executable).
Out of curiousity, what leads you to believe VB is better?
And can you recommend some good books to get started? I'm pretty good with VBA. I assume that this will help me a lot in getting started with VB.
I like the idea of using MySQL.
And can you recommend some good books to get started? I'm pretty good with VBA. I assume that this will help me a lot in getting started with VB.
I like the idea of using MySQL.
Similar threads
