aaa asked ...Is it necessary have 110 layouts?

Well, what do you think?

General Form Layouts & Windows

Main Menu (1)

Accounts Receivable (3)

Activites (2)

Address window (2) ... should be 1

Advertising (1)

Analysis Products - columnar portals by year/quarter/month (3)

Analysis Rep Commissions - columnar portals by year/quarter/month (3)

Analysis Sales Dollars- columnar portals by year/quarter/month (3)

Calculator (1)

Calendar displays (3)

Checks/Payer/Deposits window (1)

Company Information window (1)

Contact Detail (4)

Contact Sales & Product Analysis (1)

Credit Card window (2) ... should be 1

Developer layout (1)

Employee detail (2)

Error Message window (1)

Find layouts (2) ... one quick search and one advanced

General Ledger (4)

Help (1)

History & Audit Tracking (1)

Inventory (2)

Invoicing/Orders (2)

Management views (3)

NewsLetter (1)

Numbers window (1) ... phone, fax, email

Online Authorizations Importing/Exporting (1)

Payroll (6)

Preferences Management (1)

Preferences User (1)

Products (3)

Reference Materials Library (1)

Returns (2)

Rules (1)

Shipments in Process, Pending & Shipped portal window (1)

Shipping (4)

Surveys (1) ... but there is a Surveys file also.

Templates - Used to set Customer Prefs & pricing (1)

Territories (1)

Things To Do (2)

Reports, List views, Letters & forms (21) to support all of the above functions. Developer tables used by scripts and/or import/export (11).

Many of my layouts are small (appearing as popup windows) so they don't contain a lot of fields but still count as a layout. And I do NOT believe in overcrowding a layout. I enjoyed this exercise because (I believe) it assured me that the numbers aren't excessive.

The entire business is here (for the past 6 years). Our LineItems alone are 400,000 records but the overall file size is only 400MB - there are 42 tables. I use all native FM graphics and my calcs are usually lean (because I get wonderful assistance from FM Forums). We don't even have Server Advanced installed yet but every User movement and request is instantaneous. I simply don't know how I could pare it down any further and I actually have plans to add another 8-10 views.

Now, if someone had 400 layouts for a full-business solution, I might raise my eyebrows; but much depends upon what the business wants. The Analysis views provide pivot table crosstab views by Rep/Territory/Type of Product and more. No, they aren't NECESSARY but they are nice for viewing the data in various ways.

LaRetta

May be this is the back side of separatly developing. How quickly works your find scripts in table which contains 400000 records, LaRetta?

May be this is the back side of separatly developing. How quickly works your find scripts in table which contains 400000 records, LaRetta?

May be this is the back side of separatly developing. How quickly works your find scripts in table which contains 400000 records, LaRetta?

aaa said ... May be this is the back side of separatly developing.

I think you're missing the point if you're talking about the Separation Model because all layouts are in one file. And if you're suggesting having several files with layouts in each - just to deal with the layout numbers, I think that's throwing the baby out with the bathwater. In prior versions, the layouts were segmented in each file so having 100 layouts in a file might seem high. But with 7, I don't believe it is. And I'm certainly not going to split up my interface into different files; good God, that would be much more difficult to work with.

I rarely use finds and certainly not on my LineItems table. I paste IDs in some cases and write to multiline in others - then GTRR. It is 3 seconds max when performed on a workstation, regardless of the found set size.

aaa said ... May be this is the back side of separatly developing.

I think you're missing the point if you're talking about the Separation Model because all layouts are in one file. And if you're suggesting having several files with layouts in each - just to deal with the layout numbers, I think that's throwing the baby out with the bathwater. In prior versions, the layouts were segmented in each file so having 100 layouts in a file might seem high. But with 7, I don't believe it is. And I'm certainly not going to split up my interface into different files; good God, that would be much more difficult to work with.

I rarely use finds and certainly not on my LineItems table. I paste IDs in some cases and write to multiline in others - then GTRR. It is 3 seconds max when performed on a workstation, regardless of the found set size.

aaa said ... May be this is the back side of separatly developing.

I think you're missing the point if you're talking about the Separation Model because all layouts are in one file. And if you're suggesting having several files with layouts in each - just to deal with the layout numbers, I think that's throwing the baby out with the bathwater. In prior versions, the layouts were segmented in each file so having 100 layouts in a file might seem high. But with 7, I don't believe it is. And I'm certainly not going to split up my interface into different files; good God, that would be much more difficult to work with.

I rarely use finds and certainly not on my LineItems table. I paste IDs in some cases and write to multiline in others - then GTRR. It is 3 seconds max when performed on a workstation, regardless of the found set size.

And how many fields you have in thise table. I am interesting because i want to tell it to my students.

I dont suggest you to separate your file, because you did a great work and to change it will be very difficult. Sory for my English.

And how many fields you have in thise table. I am interesting because i want to tell it to my students.

I dont suggest you to separate your file, because you did a great work and to change it will be very difficult. Sory for my English.

And how many fields you have in thise table. I am interesting because i want to tell it to my students.

I dont suggest you to separate your file, because you did a great work and to change it will be very difficult. Sory for my English.

Hi aaa,

Well, umm, there are 680 fields in this file.

But that counts all calculations and globals and everything! There are 136 in Contacts, 122 in Calendar and 74 in Invoices alone (those are the largest). I have no 'like' fields in any of my tables except Rules which has 62 fields (one record; each field a rule) and Calendar which is 98% calcs and globals with many similar (day) calcs, etc. And I don't write calculations that reference other calculations so maybe that bloats the number of fields also!

I've never stood back and looked from this perspective; I'm really surprised!! I'm glad I performed this exercise, thanks! And your english is fine.

LaRetta

Hi aaa,

Well, umm, there are 680 fields in this file.

But that counts all calculations and globals and everything! There are 136 in Contacts, 122 in Calendar and 74 in Invoices alone (those are the largest). I have no 'like' fields in any of my tables except Rules which has 62 fields (one record; each field a rule) and Calendar which is 98% calcs and globals with many similar (day) calcs, etc. And I don't write calculations that reference other calculations so maybe that bloats the number of fields also!

I've never stood back and looked from this perspective; I'm really surprised!! I'm glad I performed this exercise, thanks! And your english is fine.

LaRetta

Hi aaa,

Well, umm, there are 680 fields in this file.

But that counts all calculations and globals and everything! There are 136 in Contacts, 122 in Calendar and 74 in Invoices alone (those are the largest). I have no 'like' fields in any of my tables except Rules which has 62 fields (one record; each field a rule) and Calendar which is 98% calcs and globals with many similar (day) calcs, etc. And I don't write calculations that reference other calculations so maybe that bloats the number of fields also!

I've never stood back and looked from this perspective; I'm really surprised!! I'm glad I performed this exercise, thanks! And your english is fine.

LaRetta

Love that ToC, Fenton! Thanks a million.

Love that ToC, Fenton! Thanks a million.

Love that ToC, Fenton! Thanks a million.