Moving Forms to VB

  • Thread starter Thread starter Ken K.
  • Start date Start date
K

Ken K.

Is there a way to take a Access form and import it into VB?

I am moving all my code out of my access database and into
a stand-along VB app. I have about 40 forms that I do not
want to recreate in VB.

Thanks,

Ken
 
Unfortatnly, the VB forms are rather simple as compared to ms-access forms.
Ms-access forms have about double the events as compared to the simple VB
forms. It is for this reason why ms-access forms take so much more time to
lean and master then do VB forms.

You can learn to use VB forms in much less time, since they are so simple.

VB forms are missing a lot of features like:

No on-open event. (you can't cancel the loading of the form).
You do have a on-load event in VB, and ms-access also does.

None of the data events such as on-insert, before delete, before update,
after update and zillion others DO NOT exist in VB.

The VB combo boxes don't have a "not in list event" like we do. In addition,
the native combo box for VB is NOT multi-column.

You don't have sub-forms, and thus have to resort to grid controls, or a
reccordset control and bind field to that. Really very messy.

My favourite ms-access feature is launching a form to a PARTICULAR RECORD
from a list of records in ms-access. You can do this with ONE LINE OF CODE!
in ms-access due to the where clause:

docmd.OpenForm "the form",,,"id = " & me!id

Since you don't have a "where" clause, then you can't open a VB form to a
particular record without some additional coding. I use the above feature
extensively in access. The following screen shots show this feature in
action:

http://www.attcanada.net/~kallal.msn/test/gs1.gif
http://www.attcanada.net/~kallal.msn/Search/index.html

The above is the short list, and I easily could write another 10 pages on
the difference in the forms model. And, you don't have a good report writer
in VB either!
 
Thanks for the advice Cheryl I guess I will just start
from scratch and re-do my forms.

Ken
 
Back
Top