xtrim Posted July 12, 2005 Posted July 12, 2005 Hi, I had this idea about seperation model that might be faster in most way and i wanted some opinions: The idea is to maintain seperation model GUI <-> DATA but instead of using a global/calculation field for portals, I will have the same tables in the GUI file as in the DATA file BUT with only the key field and the rest through the relationship. This way I get the following: 1 - when you have a search criteria including lots of fields, it is much easier to perform a find. 2 - no need for many complicated calculations and "mirror-like" fields 3 - easier maintanance 4 - more modular And: 1 - It is easy to sync because of the unique key per table. 2 - You still replace only the GUI file in most cases 3 - search is faster (I think...) 4 - I'll have to think about it ;-) SOO...what do you think? Is it better for the general solutions? I would also like to see some "don't do that because.." speeches...
xtrim Posted July 14, 2005 Author Posted July 14, 2005 No opinios...hmmm...it means it's perfect or complete rubish.... Don't be shy guys.....
Fitch Posted July 22, 2005 Posted July 22, 2005 I don't see what the point of this is, or why you think it would be faster. When you define a file reference, you can use tables from that file in your TOG and they act just like they're in the file you're working with. 1- easier finds, how so? 2- why do you thin those things are required? 3- the opposite, it seems to me. 4- how so?
Recommended Posts
This topic is 7075 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now