Posted 20 March 2001 - 10:48 AM
In terms of rolling regen VIP will be capable of handling all your functions and provide a collated report of failures on completion.
Posted 20 March 2001 - 03:50 PM
Do you mean pointers to the genfile code or something else?
If it really is dangerous, then surely the better design would be either (i) to split into 2 files - one that we can have access to and one that we can't, or (ii) to document the definition and tell us how to set the variables?
Posted 21 March 2001 - 10:00 AM
the initial property and value i.e forecolor - red etc
and the default record for the object which
could be field cycle etc.
if tools were written to access this file you would have to
tag de-duplication for function scope
object reference pointer maintenance (i.e. where the object is stored within the bootstraps)
default value deletes (we don't store values that returned to null states)
Failure to perform any of the above would result in behavioural issues for the function and problems within the development environments.
Although I don't doubt any decent PROIV developer could do this is it really what is required. What sort of tools do you have in mind? Should the development environment help you here?
The VIP API will allow you to write bulk search change tools and will automatically handle the ‘leg work’ above. In addition to the API a decent search and replace engine as planned for VIP should provide most of the functionality you require.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users