J
John Phelan
Goal: To improve an application's performance by basing sub forms and combo
boxes on queries:
The application has a front and back-end. There is no SQL server back-end
involved. I use a module file for, seeking out the back-end and
automatically linking to the back-end in order that I might be able to
provide updates. This has worked for me since first setting everything up.
First let me define what I mean by, “sub form†as to how I am designing my
application. I have a number of, what I call, “main (unbound) forms†that
are used to open up separate application modules. Each module contains a
number of hyperlinks to each of the other application modules. Also, each
main form (application module) contains a tab form with bound forms.
Therefore, I am calling these lower level bound forms, sub forms and basing
them on query files instead of tables. Many of the tables have fields for
collecting information across a second form. I did not want to bring back
all the fields when they are used in any of the two are three forms bound
with the same table.
Finally, there are a few forms that have either a single or sometimes two or
three synchronized combo boxes. All of the combo boxes are based on query
files, not SQL statements.
Problem: When I base a sub for on a query the front end no longer links to
the back-end database when ever a create a new/fresh version of the front-end
application involving any (what really should be the main?) form based on a
query. However, the combo boxes work.
I suspect that my problem is in what I am calling a main and sub form; and
that the main form is really the first level bound form and never the top
unbound form. I have a lot of forms. I just wanted to get some feedback on
my suspicions or find out what else could be the source of my problem befor
re-doing everything.
Thanks,
John
boxes on queries:
The application has a front and back-end. There is no SQL server back-end
involved. I use a module file for, seeking out the back-end and
automatically linking to the back-end in order that I might be able to
provide updates. This has worked for me since first setting everything up.
First let me define what I mean by, “sub form†as to how I am designing my
application. I have a number of, what I call, “main (unbound) forms†that
are used to open up separate application modules. Each module contains a
number of hyperlinks to each of the other application modules. Also, each
main form (application module) contains a tab form with bound forms.
Therefore, I am calling these lower level bound forms, sub forms and basing
them on query files instead of tables. Many of the tables have fields for
collecting information across a second form. I did not want to bring back
all the fields when they are used in any of the two are three forms bound
with the same table.
Finally, there are a few forms that have either a single or sometimes two or
three synchronized combo boxes. All of the combo boxes are based on query
files, not SQL statements.
Problem: When I base a sub for on a query the front end no longer links to
the back-end database when ever a create a new/fresh version of the front-end
application involving any (what really should be the main?) form based on a
query. However, the combo boxes work.
I suspect that my problem is in what I am calling a main and sub form; and
that the main form is really the first level bound form and never the top
unbound form. I have a lot of forms. I just wanted to get some feedback on
my suspicions or find out what else could be the source of my problem befor
re-doing everything.
Thanks,
John