K
Klaus Wiesel
Hello
I have a program which collects tables, forms and modules from different
source mbs into one target mdb and compiles the target.
All source mdbs were made with access 2000 and are compiled under access
2000.
The program runs on two access 2003 systems (both with current sps).
The same program "succeeds" on machine A (standalone win xp), but
"fails" on machine B (win 2003 terminal server).
Here "succeeds" means that if I open the MDB after the program run, the
compile menu function is grayed (= the mdb is compiled)
I experienced that when I compile all of the source mdbs before the
program runs on machine B the target is compiled too.
This step is not necessary for machine A.
Are there any known conditions for the compile to succeed?
All runs have been made with local admin rights.
Regards
Klaus Wiesel
I have a program which collects tables, forms and modules from different
source mbs into one target mdb and compiles the target.
All source mdbs were made with access 2000 and are compiled under access
2000.
The program runs on two access 2003 systems (both with current sps).
The same program "succeeds" on machine A (standalone win xp), but
"fails" on machine B (win 2003 terminal server).
Here "succeeds" means that if I open the MDB after the program run, the
compile menu function is grayed (= the mdb is compiled)
I experienced that when I compile all of the source mdbs before the
program runs on machine B the target is compiled too.
This step is not necessary for machine A.
Are there any known conditions for the compile to succeed?
All runs have been made with local admin rights.
Regards
Klaus Wiesel