Prev: Picture Orientation
Next: Accessing the Data Connection Strings and Command Text (SQL) i
From: Sarah on 30 Apr 2010 15:37
How can I avoid this message when running my macro. The value(s)that came
from a BusinessObjects Enterprise data source has just been edited/deleted.
Do you want to proceed with the change? I have tried setting displayalerts to
false.
From: Jim Thomlinson on 3 May 2010 16:28
Nothing you can do about that message. It is part of BO and not of Excel. I
am not sure if there is anything in the BO API to avoid the message.
--
HTH...

Jim Thomlinson


"Sarah" wrote:

> How can I avoid this message when running my macro. The value(s)that came
> from a BusinessObjects Enterprise data source has just been edited/deleted.
> Do you want to proceed with the change? I have tried setting displayalerts to
> false.
From: Sarah on 17 May 2010 09:28
I discovered by accident that if the excel ss that gets its data from the BO
report is saved as an earlier version of excel, and then resaved as excel
2007, the problem disappears. That suggests that whatever BO communicates to
excel is not communicated to the earlier version. I can report that I did
not have the problem before moving to excel 2007. (Same macro, data from
same version of BO.) It makes me nervous to make that "Save,save" part of
the process because I don't know what else might be happening when I do it.

"Jim Thomlinson" wrote:

> Nothing you can do about that message. It is part of BO and not of Excel. I
> am not sure if there is anything in the BO API to avoid the message.
> --
> HTH...
>
> Jim Thomlinson
>
>
> "Sarah" wrote:
>
> > How can I avoid this message when running my macro. The value(s)that came
> > from a BusinessObjects Enterprise data source has just been edited/deleted.
> > Do you want to proceed with the change? I have tried setting displayalerts to
> > false.
 | 
Pages: 1
Prev: Picture Orientation
Next: Accessing the Data Connection Strings and Command Text (SQL) i