Prev: SQLMaster conversion is slow
Next: Webservice Server
From: Eckhard Sallermann on 3 Aug 2010 07:36
VO 2.8 SP3 B 2836 / Excel 2003 SP3

i am running a VO 2.8 App, in this app i open a exceltable and fill it
with data. Opening an other table during this the table, i use with VO
OLE will getting visible, how can i prevent this ??

another problem is, that after oExcel:quit() the excelprocess will
running on, soetimes it helps, moving the appwindow to realy quit the
excelprozess !?!?!

i set fROTCHECK to FALSE

METHOD Init(ObjID, fROTCHECK) CLASS _Application

IF (ObjID=NIL)
ObjId := "Excel.Application.11"
ENDIF
sUPER:Init(ObjID, 0, .T., fROTCHECK)

SELF:_dwFuncs := 378
SELF:_dwVars := 0
RETURN SELF




From: Nick Friend on 3 Aug 2010 09:20
Eckhard,

Something like this when you finish using Excel should remove it from
memeory... if you google this on the newsgroup you'll find loads of
people have had the same problem.

oMSExcel:Quit()
oMSWorkBooks:=NULL_OBJECT
oMSExcel:=NULL_OBJECT

I got fed up trying to support integration with Excel and since we
only need to read and write XLS files (rather than reporting in Excel
for example), we now use this utility instead - http://sm-software.com/index.htm.
It's cheap and very very fast for reading and writing XLS files. Worth
a look.

HTH

Nick



On 3 Aug, 12:36, Eckhard Sallermann <eckhard.sallerm...(a)bur-kg.de>
wrote:
> VO 2.8 SP3 B 2836 / Excel 2003 SP3
>
> i am running a VO 2.8 App, in this app i open a exceltable and fill it
> with data. Opening an other table during this the table, i use with VO
> OLE will getting visible, how can i prevent this ??
>
> another problem is, that after oExcel:quit() the excelprocess will
> running on, soetimes it helps, moving the appwindow to realy quit the
> excelprozess !?!?!
>
> i set fROTCHECK to FALSE
>
> METHOD Init(ObjID, fROTCHECK) CLASS _Application
>
>      IF (ObjID=NIL)
>          ObjId := "Excel.Application.11"
>      ENDIF
>      sUPER:Init(ObjID, 0, .T., fROTCHECK)
>
>      SELF:_dwFuncs    := 378
>      SELF:_dwVars     := 0
>      RETURN SELF

From: Eckhard Sallermann on 3 Aug 2010 11:15
Hi Nick,

thanks for your response, i will have a look at it


Am 03.08.2010 15:20, schrieb Nick Friend:
> Eckhard,
>
> Something like this when you finish using Excel should remove it from
> memeory... if you google this on the newsgroup you'll find loads of
> people have had the same problem.
>
> oMSExcel:Quit()
> oMSWorkBooks:=NULL_OBJECT
> oMSExcel:=NULL_OBJECT
>
> I got fed up trying to support integration with Excel and since we
> only need to read and write XLS files (rather than reporting in Excel
> for example), we now use this utility instead - http://sm-software.com/index.htm.
> It's cheap and very very fast for reading and writing XLS files. Worth
> a look.
>
> HTH
>
> Nick
>
>
>
> On 3 Aug, 12:36, Eckhard Sallermann<eckhard.sallerm...(a)bur-kg.de>
> wrote:
>> VO 2.8 SP3 B 2836 / Excel 2003 SP3
>>
>> i am running a VO 2.8 App, in this app i open a exceltable and fill it
>> with data. Opening an other table during this the table, i use with VO
>> OLE will getting visible, how can i prevent this ??
>>
>> another problem is, that after oExcel:quit() the excelprocess will
>> running on, soetimes it helps, moving the appwindow to realy quit the
>> excelprozess !?!?!
>>
>> i set fROTCHECK to FALSE
>>
>> METHOD Init(ObjID, fROTCHECK) CLASS _Application
>>
>> IF (ObjID=NIL)
>> ObjId := "Excel.Application.11"
>> ENDIF
>> sUPER:Init(ObjID, 0, .T., fROTCHECK)
>>
>> SELF:_dwFuncs := 378
>> SELF:_dwVars := 0
>> RETURN SELF
>

 | 
Pages: 1
Prev: SQLMaster conversion is slow
Next: Webservice Server