Hi,
In general, resources over 10000 are system resources in the Boot
database, which are always loaded.
If you have >10000 resource IDs that you use, the OS will load your
resources by default and only fallback to Boot resources if it can't
find a matching ID.
So it shouldn't be a source of your issue.
~Ryan Rix
TamsPalm
griffariff wrote:
When creating a new resource (form, alert, menu bar, menu, etc) in
Constructor, the ID is automatically incremented by 100. For
example the first form is 1000, then 1100, 1200, etc. Is it safe to
increment IDs by 10 in the case of Alerts and Bitmaps and such? In an application I am servicing I have found that there are a lot of IDs over the 9999 barrier: an Alert ID over 15,000, a menu ID over 10,000, Bitmap Family IDs over 18,000 and BitMap IDs over 20,000.
What is the expected behaviour for these conditions? The
application has been experiencing relatively random Fatal Alerts. Is this a potential source? What does the OS reserve IDs over 9999 in realtion to the runtime of an application?
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
