Migrate FE to different development environment

[Guest]

Not sure this is the right place or the right questions...I have a FE/BE
application that has a sigifcant amount of VBA code in the FE along with
forms and I thinking I need to move it to a different development environment
to reduce the size (mde is about 12mb), ease of maintenance and upgrades and
improve compatabilty with other environments (ie MAC, Web based).

Is there a "best" solution that I can use to reuse my code and forms - I
have looked into .Net and there seem to be issues with listbox (I use them
extensively). Should I look at VB6 and if so what draw backs are there?

Any suggestions or insights would be greatly appreciated!

Thanks in advance - Jerry

 

[Albert D. Kallal]

Are you using any background graphics for your application?

I have an access application with 160 forms, about 28,000 lines of code,
77 reports, and about 190 quires.

The whole mde is only 6.4 megs. And zipped, it fits on a floppy disk (1.4
megs)

So, if your mde is actually 12 megs, it still not that large (only about
double the
size of the above mentioned application. And, I consider my application
"medium" sized, certainly not large.

Is there a "best" solution that I can use to reuse my code and forms - I
have looked into .Net and there seem to be issues with listbox (I use them
extensively). Should I look at VB6 and if so what draw backs are there?

Well, we have not seen new version of VB6 for years..(I think we seen at
least
two, and now we are seeing the 3rd *NEW* version of ms-access released since
VB6 came out). So, I don't think VB6 would be a really useful path since no
new versions are coming out.

If I were to re-write, I would go the .net approach, as then you can also
move towards web based solutions.

Any suggestions or insights would be greatly appreciated!

Well, I don't think, nor see an advantage to moving this to VB6, as it would
take a rather large amount of work, and the end result would be not much of
a advantage I can see. After spending huge amounts of time, you would now
have an application that runs in vb6...and what have you accomplished?

It really comes down to were you think the future of this appcation needs to
go. Does it need some web parts? Is it multi-user..and you are reaching the
limits of the application?

I would as mentioned check if you have any graphic backgrounds for the
forms...if you remove those backgrounds..I seen file shrink by rather large
amounts.

My users never care much (or in fact even know) that the application is in
ms-access. If your application is a success, and it is doing your job for
you, then why change?

 

[Guest]

Albert,

Thanks for your insights - I will check on the background graphics to see if
that is the issue. I have about 25 forms, about 35,000 lines of code, a few
reports and queries so I am not sure why it is so big.

I am starting to getting users that want web-based functionality so the .net
route seems to be the most logical. I would like to be able to re-use my
code and find a way to "export" my forms to use in .net - not sure if that is
possible.



Thanks-Jerry