When Small mailing list opens, its .Init procedure is not triggered until after the “TestBed init completed” message appears. This is a bother because I want the process to end up with the * mfg_winnam* window on top but I always end up with the “Test Form” window on top. Is this expected behaviour?
Some of you will be aware that my desktop Mac is seriously neurotic. This has become so annoying that, in desperation, I’ve bought a Macbook Pro to double-check all peculiar behaviour. It does the same as described above. If it’s also off its trolley, I’m going to be seriously annoyed.
They both work - thanks Dave. I had to use the second one because my procedure won’t know the name of the form opened by the target database (indeed, it won’t even know whether there is a .Initialize procedure) so the code with the call .Initiallize is perfect - I just had to add an if error test after it.
When there’s no .Init and/or no form, the target d/b remains secret which I had thought might be a problem because the code I sent initially is triggered by a PopUp Button Object in my crosstab emulator. This goes on to save the d/b under another name and carry out lots of complex processing but everything works seamlessly - so far