From: Meinhard Schnoor-Matriciani on 19 Mar 2007 16:10 Michael, you should add o:setmatchlogoninfo(true) after you called LogonOnServer(). I don't know if that help's ( we're using CR >= 9 ) directly. I would suggest that you update to at least version 9 ( there have been some changes in this area ). HTH Meinhard P.S.: If this does not help, try to loop to your report objects ( tables and subreports ) and on that objects call :deleteall() on the access connectionproperties and the set them via the method setlogoninfo ( that's the way it work with CR >= 9
From: Michael Haensch on 21 Mar 2007 10:02 Hallo Meinhard, > o:setmatchlogoninfo(true) does not help. With updating you're right. I've already Crystal XI on my PC, and now it's time to change .. The first test with my 5333-function gives NO error with XI. Thanks. Michael Meinhard Schnoor-Matriciani schrieb: > Michael, > > you should add > > o:setmatchlogoninfo(true) > > after you called LogonOnServer(). I don't know if that help's ( we're using > CR >= 9 ) directly. I would suggest that you update to at least version 9 > ( there have been some changes in this area ). > > HTH > Meinhard > > P.S.: If this does not help, try to loop to your report objects ( tables and > subreports ) and on that objects call :deleteall() on the access > connectionproperties and the set them via the method setlogoninfo ( that's > the way it work with CR >= 9 > > >
First
|
Prev
|
Pages: 1 2 Prev: Polygon Area (Graphics4VO?, other packages?) Next: Error 5018 When using ADSADT.RDD Driver |