Re-create a Database in VB2008?

[efandango]

I have created a database in Access 2007, but now want to distribute it to
other users. Previous version of access would allow me to make a runtime
version, but it seems this feature is no longer available in Access 2007. So…
I guess I will have to try an re-create the whole thing in Visual Basic 2008.

I’m not an advanced coder/programmer, and have often relied on the kind and
generous help from so of the experts on this forum; So my general question
are:


Is ‘pure’ VB it really that much different from using the Access development
environment/Access VBA?

Can I use things like Subforms, and QBE, Combobox wizards for control
sources, or does the whole VB environment require everything to be ‘hand
made’?

I really don’t know what else to ask in relation to this issue/concern, so
perhaps it is best to generally ask what are the pitfalls, and where might I
come up against a hard wall relative to the Access experience?

 

[Dirk Goldgar]

I have created a database in Access 2007, but now want to distribute it to
other users. Previous version of access would allow me to make a runtime
version, but it seems this feature is no longer available in Access 2007.

What makes you think this is so? Access 2007 allows you to make ACCDE
files, which are its equivalent of the MDE, and you can download the Access
2007 runtime module for free. The only thing is, your database has to be in
the Access 2007 file format, not in one of the older formats.

So…
I guess I will have to try an re-create the whole thing in Visual Basic
2008.

I think you're jumping to a conclusion here, as well as biting off a very
big mouthful.

Is ‘pure’ VB it really that much different from using the Access
development
environment/Access VBA?

Yes, enormously.

Can I use things like Subforms, and QBE, Combobox wizards for control
sources, or does the whole VB environment require everything to be ‘hand
made’?

VB 2008 has wizards and templates for its own controls and constructs, but
these are not really similar to the Access objects with which you are
familiar. And it does not have any built-in support for subforms.

I really don’t know what else to ask in relation to this issue/concern, so
perhaps it is best to generally ask what are the pitfalls, and where might
I
come up against a hard wall relative to the Access experience?

In addition to the specialized controls that Access provides, it does all
the work of data binding for you. VB, in any of its versions, doesn't do
that for you.

 

[efandango]

Gulp!... whimper... !&*"

The problem is that I have creted my DB in access, and have had people ask
me for a copy of it, but they don't have access.

Is there anything that will compile the whole thing into a neat runtime
version. Microsoft thoughfully removed that feature from Acess 2007.

Your helpful comments I guess tell me that it is going to be too tough to
create a VB solution. Life, eh?...

 

[Dirk Goldgar]

Gulp!... whimper... !&*"

The problem is that I have creted my DB in access, and have had people ask
me for a copy of it, but they don't have access.

Is there anything that will compile the whole thing into a neat runtime
version. Microsoft thoughfully removed that feature from Acess 2007.

No, they did not -- in fact, they made it easier. Please reread my earlier
reply. Access 2007 has the exact same run-time functionality of all
previous versions. No version of Access has ever had the ability to make a
standalone executable module. It has always been the case that, in order to
run any Access database, whether MDB or MDE, you had to have either Access
or its run-time module installed -- the run-time module being essentially
the whole Access application with all the built-in user-interface features
disabled.

Previously, you could only get the Access run-time module by purchasing the
Developer's Edition or Developer's Toolkit (depending on the version). With
Access 2007, the run-time module is available as a free download.

The developer's edition/toolkit does include the Packaging Wizard, which
makes it easier to package your application and all required files
(including the run-time module) into one install package. However, that is
not always necessary.

Your helpful comments I guess tell me that it is going to be too tough to
create a VB solution. Life, eh?...

Too tough? That depends on how much effort you want to put into it. But it
won't be nearly as easy as Access.