General information
Category:
Object Oriented Programming
Title:
Practical limit of Properties on goApp
My Application Object has all of the details of the application, including the name of the app (for the splash screen), the month and year we're currently working on (goes in form captions and on reports), the IP address of server we import our data from, the names of the files to import, etc. etc. etc.
I keep all of this stuff in a table and add it to goApp after I instantiate the object.
Now I'm adding reports. They have titles, footer text, and may have footnote text. That means about 20 more properties. Obviously I could create a goReports if I needed to keep from overloading goApp.
Is there any reason not to have 100 properties on goApp? Any reasons to have a separate goReports for the report-related stuff?
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only