Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About BriSchnei

  • Rank
  1. When one user modifies a field and commits the record, other users that have that field/record in the current found set have their browsers suddenly and completely refreshed/redrawn. This uniquely bothers the WD users since the entire browser window is redrawn. The concurrent FMP users just receive the data update with minimal interference. Any thoughts on how to avoid this are appreciated thanks
  2. Comment, The main reason that a relational model utilizing portals wasn't implemented here was because I inherited this db from a previous developer. The backbone of the system is the resources' statuses so I've been avoiding the prospect of rebuilding the whole thing (many layouts, scripts, calculated fields, etc). Regarding Extend(), where do you suggest? I have two repeating calculated fields: a) Activity_Resource Names[] = GetValue( Extend(Activity_Resources) ; Get( CalculationRepetitionNumber ) ) CurrentStatuses[] = GetField("ResourceStatus_" & Activity_Resource Names
  3. In order to build a very dynamic layout I have the following scenario: Users can select multiple "Resources" from a checkbox set and then the associated text label and icon will appear elsewhere on the layout for each selected resource. Also, each resource has a status associated with it (e.g., new, updated, cancelled); the aforementioned icon for each resource will be determined by that resource's current status. It works as follows: 1) User selects 0...n "resources" from a checkbox set (i.e., Resource1, Resource2, ...). This is stored in the field "Activity_Resources" 2) E
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.