G
Guest
Ever since I successfully applied some techniques for increasing the speed of
my 17 meg. Application; it has only made me hunger for more. First, let me
list what I have done so far:
1. Split the application and database into front and back-ends,
2. Increased the load-time of my application by “pre-loading my heaviest
forms when the database is initially opened,
3. When forms do open, under, “Filter Lookup†I use, “Neverâ€,
4. I set my combo boxes under “auto expand†to “noâ€,
5. I have discovered that fonts can make a significant difference in
“large†applications. For example; if you measure the file size of folders
for each of Window’s font types for lightening your application’s
size/weight, “Microsoft Sans Serif†does not take up as much memory. Again,
the benefit from using Microsoft Sans Serif is more apparent in larger
databases. However, using, Microsoft Sans Serif in applications, make fonts
more visible/clear on LCD screens; even with “Clear Type†turned on. Another
benefit in using this font-type is that I no longer have a need to use bold,
which uses more memory. Also, using Microsoft Sans Serif, with larger fonts
for main titles gives it a sharper bold look than using bold type for other
same font size.
6. I created “query files†for using only table fields that are needed in a
particular form.
These are just a few, apart from suggestions applied from using the, FMS
Total Access Analyzer, that I used for speeding up my application.
However, let get peoples opinions on a couple of thoughts for furthering my
application’s speed :
A. There are three or four groups of linked tables in my database that are
not linked to any other part of the database except for using lookups i.e.,
employee’s names and locations. In the event that I upsize my database to
SQL at a later time, would it be more beneficial, for application speed, to
take some of these, near self-containing groups of tables, and place them in
multiple groups of back-ends, i.e., employee information vs. client private
information and their treatment schedules? Also,
B. If I were to take my form specific query files (over 200), and convert
them to SQL statements instead of using query files; would that help in, a)
reducing the size of my front-end application, speed up my application, and
ease the process of later upsizing my application/database?
John
my 17 meg. Application; it has only made me hunger for more. First, let me
list what I have done so far:
1. Split the application and database into front and back-ends,
2. Increased the load-time of my application by “pre-loading my heaviest
forms when the database is initially opened,
3. When forms do open, under, “Filter Lookup†I use, “Neverâ€,
4. I set my combo boxes under “auto expand†to “noâ€,
5. I have discovered that fonts can make a significant difference in
“large†applications. For example; if you measure the file size of folders
for each of Window’s font types for lightening your application’s
size/weight, “Microsoft Sans Serif†does not take up as much memory. Again,
the benefit from using Microsoft Sans Serif is more apparent in larger
databases. However, using, Microsoft Sans Serif in applications, make fonts
more visible/clear on LCD screens; even with “Clear Type†turned on. Another
benefit in using this font-type is that I no longer have a need to use bold,
which uses more memory. Also, using Microsoft Sans Serif, with larger fonts
for main titles gives it a sharper bold look than using bold type for other
same font size.
6. I created “query files†for using only table fields that are needed in a
particular form.
These are just a few, apart from suggestions applied from using the, FMS
Total Access Analyzer, that I used for speeding up my application.
However, let get peoples opinions on a couple of thoughts for furthering my
application’s speed :
A. There are three or four groups of linked tables in my database that are
not linked to any other part of the database except for using lookups i.e.,
employee’s names and locations. In the event that I upsize my database to
SQL at a later time, would it be more beneficial, for application speed, to
take some of these, near self-containing groups of tables, and place them in
multiple groups of back-ends, i.e., employee information vs. client private
information and their treatment schedules? Also,
B. If I were to take my form specific query files (over 200), and convert
them to SQL statements instead of using query files; would that help in, a)
reducing the size of my front-end application, speed up my application, and
ease the process of later upsizing my application/database?
John