some thoughts... (see inline)
On 04/01/2014 06:57 AM, Marion & Noel Lodge wrote:
In opening my database accounting system, I trigger via the Form: When
loading event, a macro, (Sub Init()), containing the database
As the Form loads it displays the first record in the database,
the account number. To make things easier for the user, the Text
event on the account number control, triggers a macro, (Sub AccName()),
that displays the account name.
And I assume that this is built into the form.
Sometimes the system has crashed because it seems that Sub AccName()
fired before Sub Init() has finished. (Sub AccName() depends on some of
the structures that Sub Init() sets up.)
Is it possible that both Subs are running in parallel or do they always
in series on a first come first served basis?
Warning: Speculation... So insert the following text before each
below: "I am making a wild unsubstantiated guess that"
1. The form is populated before Init() finishes
2. AccName() is called as soon as text is pushed into the control.
So, if this is the case, then AccName may be called before Init()
finishes. If you really want to know if they run at the same time, you
could do a not so quick test and modify each routine so that the macro
something like this:
Write current time to a file
delay a second or two
Do the work
delay a second or two
Write the current time to a file
Use a different file for each subroutine, then compare the start and end
time to see if they overlap. You can probably get away with using a
print statement at the start and end.
If the latter, are there coding techniques that can be used to ensure
Sub Init() always runs first?
If things run serially and AccName is called based on something done in
Init(), it may be possible that Init() cannot complete until after
I suppose that another possibility is to set a "Global" variable such as
"InitComplete". set to false when Init() starts, and set to true when it
completes. Modify AccName to check for InitComplete. If things are
then you may need to simply return. If not, then have AccName wait for a
few seconds and try again. If things are truly serial, then I would
them to fail every time, and they don't fail every time, so it is likely
not the case.
If the former, how can I ensure that Sub AccName() waits until Sub
Oh wait, see above! :-)
Can someone point me to any articles on this subject?
My Macro Document: http://www.pitonyak.org/AndrewMacro.odt
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be