Building an App Workflow

[DawnTreader]

Hello All

i have a quick question.

when building an application that is made up of many different "modules" or
"work types" is it a good idea to build a separate frontend and then merge it
later?

for instance if i have an application that handles orders and now we want to
add inventory would it be good to build the inventory module as a separate
frontend and when it is ready to merge it with the existing frontend for
orders?

i have an app that i have been building for around 2 years and it is getting
to be rather large and i was thinking this might help in keeping the
managiblitity of the new module under control.

any thoughts?

 

[Fred]

I tend to think that the answer will be based on the particulars rather that
a general one. Others who respond to these will know the answer better than
me with respect to code, Access objects etc.

My comment is more about where you are headed with your particular
example.....you are basically building an enterprise application, which it is
functionally more complex than 99% of Access applicaitons, dealing with
transactions as entities. For that, I would recommend considering your
"modules" to be very separate functionally, to the point where you document
their inputs and outputs separately as well as interactions with other
modules. If you do that, you might have a better product than commercial
enterprise applications which often only get partially implemented/ used
because they become "black boxes" with "fuzzy" behavior which makes users
not like or trust them.

 

[DawnTreader]

Hello

my inabilty to communicate stymies me again.

this is a frontend / backend system. what i am asking is would it be
benificial to create a new module as a seperate frontend from the existing
frontend to manage the creation of the new module and then merge it with the
existing frontend later?

sorry for not being clear about hte frontend / backend situation in my first
post.

 

[Stanley and Evelyn Lipkin]

Unsubscribe now

Hello

my inabilty to communicate stymies me again.

this is a frontend / backend system. what i am asking is would it be
benificial to create a new module as a seperate frontend from the existing
frontend to manage the creation of the new module and then merge it with the
existing frontend later?

sorry for not being clear about hte frontend / backend situation in my first
post.

 

[DawnTreader]

Ok, with that settled, new question.

i have a few different "modules" that look at the same information, part
lists.

i need to filter part lists in different ways in different modules.

for example i manage parts for 2 different part line types, compressors and
dispensers.

for the most part i can use one query for most of what i need, but there are
now things that are particular that i am doing to one that i am not doing to
the other list of parts.

should i duplicate queries and make the necessary alterations, or should i
be finding ways to filter based on product types? understand what i am
explaining is simplified, but my question is, is it more efficient to have
one set of queries that i filter through different means to get my end
result, or should i just duplicate queries and put in different criteria for
each set of results that i need.

i have a feeling i wont get the kind of answers i am expecting, but i can
clairify as needed.