Access program size

M

MJJ

Is an older application that is 40,000 lines of code (written in Delphi) an
acceptable size for redeveloping directly in Access.
 
G

Graham R Seach

MJJ,

The only things that I know of that you can do in Delphi, that you can't do
in Access are:
* Threading
* Create .exe or .dll files (or any others except .mdb, .mde, adp, ade).
* Real polymorphism

As I understand it, there are also several things that you can do in Delphi,
but can't do in any Microsoft environment. MVP Peter Walker uses Delphi, so
he can tell you what they are (if he has his ears on).

40,000 lines of code isn't a problem.

Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia

Microsoft Access 2003 VBA Programmer's Reference
http://www.wiley.com/WileyCDA/WileyTitle/productCd-0764559036.html
 
A

Albert D. Kallal

It turns out, if the developer knows ms-access well, then likely the number
of lines of code will drop drastically.

I converted a fairly complex application from a business basic mini computer
system\ to ms-access. The stats were in lines of code::

User interface: 34964
Program logic (business rules) 28816
Data entry verification 3143
Reports 16561
=====
80341

After converting the above to ms-access, we resulted with:

lines of code in Modules = 8670
Lines of code in forms = 16409
Lines of code in reports = 2290
============
total lines of code = 27369

So, as a general rule, the lines of code will drop. I would actually pay
more attention as to how many forms you have.

The ms-access application resulted in 160 forms....

So, the resulting ms-access application was a medium in terms of size and
complexity.
 
M

MJJ

Thanks you for the information. A few other general questions. Are there
any issues with speed in an application of this size in Access and the
ability to use it in a small (3?) multiuser environment.

MJJ
 
A

Albert D. Kallal

Thanks you for the information. A few other general questions. Are there
any issues with speed in an application of this size in Access and the
ability to use it in a small (3?) multiuser environment.

MJJ
Click to expand...

Performance is really much a art when it comes to software. We often get
posts here about how some form loads too slow..and that is with ONE person!

In the range of 3 to 10 users, and small tables (say 150,000 records), then
this kind of application is a sweat spot for ms-access.

The thing you want to ensure is that you learn about how ms-access needs to
be setup in a multi-user environment. This means that you installed the
"software" part of the ms-access application on each pc (this is usually
called the Front End, and should be a mde). And, then these FE link to the
back end (BE), which is a mdb file. This ensures a reliable multi-user
setup. You can read about his here:

http://www.granite.ab.ca/access/splitapp.htm


By the way, I have a paper and some documenting on the conversion process
that I used and went to when I converted that application to ms-access.

You can read about this conversion here:
http://www.attcanada.net/~kallal.msn/Articles/fog0000000003.html

The above will give you some insights and ideas that will prove valuable in
your conversion attempt.
 
T

Tony Toews

Albert D. Kallal said:
In the range of 3 to 10 users, and small tables (say 150,000 records), then
this kind of application is a sweat spot for ms-access.
Click to expand...

You been working out or something? <smile>

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Top