Access Runtime vs VB object converters?

  • Thread starter Thread starter Titlepusher
  • Start date Start date
T

Titlepusher

I have written a few applications in MSAccess over the years starting with
my first in v2.0. I am not a coder in any way, but do have some monster
applications. I have upgraded to 97dev then Office XPdev along the way. I
would like to sell and distribute some of them. They can all be upgraded. I
have used the packaging wizard a few times with some success.

I have read many of the posts in this forum re: the run time and packaging
wizard, version issues and I see that there are many viewpoints and tools
such as SageKey which users like to package their apps.

My question is has anyone used the .mdb to VB converters? From what I
understand they turn your .mdb app into an executable. Can they can
eliminate some of the Access version issues? Are they stable? Any
replies appreciated.

tp
 
hi,
My question is has anyone used the .mdb to VB converters? From what I
understand they turn your .mdb app into an executable. Can they can
eliminate some of the Access version issues? Are they stable? Any
replies appreciated.
Click to expand...
There is no such a thing like an Access compiler. You may use SageKey to
manage your deployment.

The only way to get an executable file, is to use for example VB.NET and
redevelop your applications.


mfG
--> stefan <--
 
I did a quick google on VB object converters and I see the product that I
think you are talking about. While I have never used this Access to VB
tool, I would guess it's not as easy as advertised to take a complete
Access application and switch it to a VB or VB.NET application. Reporting
for one in VB or VB.net usually works with a different product other than
Access. Your back-end access database can probably stay the same, but
front-end functionality would be written differently based on access or
VB/VB.net/C#. Controls are a bit different between the two environments
etc.... The product probably helps convert VBA to VB syntax.

I would opt for Access2007 runtime and stay the Access course.

For installation tools try this article:
http://www.members.shaw.ca/albertkallal/RunTime/Index.html

I hope to soon finish my first real commercial app written in Access2007
(using the runtime). Hopefully it will be done within the next few months.
I ended up just purchasing sagekey's product (but haven't used it much yet).
I promised them an article on their product (in exchange for a discount).
Not sure yet how much Sagekeys product helps.

Note: Using Access alone or (.net and access database) both have pros and
cons.
The Access runtime is pretty big and you have that Access2007 not getting
along well with Office 2003 issue but development is a bit faster and
certain things are much easier going the Access route. .net is more
flexible and more of the traditional route for commercial software
development (more third party controls etc...).

Would love to see your apps that you have hopes to sell. I've looked at
lots of applications for sale out there, I could give you an opinion on how
market ready they are, if you are interested. You indicated you are not a
coded so that scared me a bit. My apps tend to have tons of code. Send me
an email if interested. See my site for contact info.

Mark
RPT Software
http://www.rptsoftware.com
 
Back
Top