Re: Distributable Commercial Apps Access Vs Delphi
- From: John Mishefske <jmishefskeNO@xxxxxxxxxxxxx>
- Date: Thu, 29 Mar 2007 21:07:52 -0500
ApexData@xxxxxxxxx wrote:
I am considering building some distributable commercial applications.
For about a year now, I have been using Access2000. This was my first
venture into object oriented database development. Having a
background in Pascal and some C++, I would have preferred those
languages, but VBA made do. The SQL was fine.
I believe that Security issues on the backend, and data integrity/
corruption complaints over the network may be a stumbling block to a
solid distributable application? I am also discouraged by the
inability to make a truly compiled executable .exe front end. I have
recently read a bit about Delphi, that seems to cover these issues,
but am sure that Delphi may have its own share of issues.
Should I build marketable apps with Access on Jet or SQL, or Delphi on
Jet or SQL, or some other animal that addresses my concerns???
Apex - here's another opinion fwiw...
Someone mentioned that if you go with Delphi you'll still need a database and that's true. The real question is do you want to use Access and VBA to design the UI.
Lot depends on your target audience. If you know they have Access installed then perhaps Access/VBA is one possible solution. If the target PCs don't have Access then you'd need to use the Runtime and I'd recommend that you avoid that.
Distribution using the Runtime is more complex although, if you have the $$, I hear SageKey makes distributing the Runtime less support-intensive.
You could use an Access .mdb database to store the data without the need to distribute the Runtime version to users who don't have Access installed (although you may need to include the MDAC package in your installer to get the appropriate support code to use with the ..mdb from code). So the .mdb database is one way to store persistent data. If you don't use Access you'll need to find another way to store the data. If you need to support a large number of users or performance is crucial then SQL Server may be appropriate. If you are developing "on the cheap" you could look into open source databases like mySQL or PostgreSQL.
I haven't used Delphi; if you have experience with that then perhaps that's a better choice. But it sounds like your VBA experience would make a move to VB.Net a better choice. While substantially different from Access/VBA, it still has a lot of similarities that will ensure your are developing solutions faster than a switch to a different language. And, of course, you can create an executable file.
The vb.net compiler is part of the freely downloadable .Net framework so you can create (simple) apps with that but the VB.Net 2005 IDE will make you much more productive.
But this is a generalization; a lot depends on your application requirements, your budget and other factors. Good luck.
--
'---------------
'John Mishefske
'---------------
.
- Follow-Ups:
- Re: Distributable Commercial Apps Access Vs Delphi
- From: Rick Brandt
- Re: Distributable Commercial Apps Access Vs Delphi
- References:
- Distributable Commercial Apps Access Vs Delphi
- From: ApexData@xxxxxxxxx
- Distributable Commercial Apps Access Vs Delphi
- Prev by Date: Logout idle users and discard changes
- Next by Date: Re: This newsgroup interface is old ... we need a new forum.
- Previous by thread: Re: Distributable Commercial Apps Access Vs Delphi
- Next by thread: Re: Distributable Commercial Apps Access Vs Delphi
- Index(es):
Relevant Pages
|
