Jump to content
Sign in to follow this  
antitesi

Develop complex application

Recommended Posts

antitesi

Hello to all and it compliments for this forum.

I would want to migrate an M$Access application (rather blown) in AutoIt, but .....

1 - in order to facilitate the maintenance they must be had several modules

2 - every module can have more forms

3 - every module must communicate with the others, according to the application workflow

my solutions/thoughts:

1 - no problem: i can make several small "compiled" programs (exes)

2 - ...I have some doubt with Koda and several forms into same program......

3 - no problem: the passage of parameters between programs is possible...

thoughts, observations, critics, are welcome....

Tanks in advance....

P.S. sorry for my poor english

Share this post


Link to post
Share on other sites
junkew

How big is your MS Access application? Whats the intention personal use or large department in an organisation?

If its big in terms of

# of tables involved

# of screens designed

# of reports made

I certainly would doubt if AutoIt is then a good choice looking on development speed within AutoIT compared to MS Access point and clicking interface application.

Share this post


Link to post
Share on other sites
antitesi

How big is your MS Access application? Whats the intention personal use or large department in an organisation?

If its big in terms of

# of tables involved

# of screens designed

# of reports made

I certainly would doubt if AutoIt is then a good choice looking on development speed within AutoIT compared to MS Access point and clicking interface application.

...some numbers of application (at this moment):

A) database

# tables ===> 8 for main database (#records 150.000 per year), 15 for parameters

:P main user interface (# users ===> 20-25)

# screens/subscreens ===> 35

# reports ===> 6

# modules ===> 6

C) service module (import/export external files into/from database)

# screens/subscreens ===> 15

# reports ===> 2

# modules ===> 6 (same as "main user interface")

working in LAN, not in large departement

and, yes i agree with yuor observation about "speed development", but after this initial "speed", the architecture of M$Access forces me to make some "strange trick" to get a good result (in fact the application, easily, grows)

This influence the speed of development, and the performances of the application, also

With AutoIt there are few things that have need of "trick"(compare to Access VBA), the realization/coding is very more direct...

I think that AutoIt is strong enough to develop more complex applications of some automation, but that it should improve some very important aspects, as:

1 - management of the projects (development for multiple modules)

2 - management of more forms in the same program

3 - management of the reports (it doesn't serve something of sophisticated like Cristal Report, but of basic, like the old Clipper...)

I don't know if this is the direction that the development of the product can take (personally I would like...).

I believe that this product deserves even more an ample use of the actual one........

P.S. once more, sorry for my English...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.