"Barry Williams" <barry.r.williamsnospam@saic.com> wrote in message <kuai3m$qf5$1@newscl01ah.mathworks.com>...
> "Nick" wrote in message <ku9vbj$h1u$1@newscl01ah.mathworks.com>...
> > dpb <none@non.net> wrote in message <ku8r0r$eoj$1@speranza.aioe.org>...
> > > On 8/11/2013 2:54 PM, TideMan wrote:
> > > ...
> > >
> > > > Did you check sheet A1:B2, if that is in fact a legal name for a sheet in Excel?
> > > > Because that's what you've told xlswrite the sheet name is.
> > >
> > > Good catch TM--one just presumes since the argument is a range that it's
> > > ok when in fact it likely isn't. I don't use Excel enough but I'd bet
> > > that's probably the case.
> > >
> > > I was just going to suggest OP try w/o the range just on general
> > > principles of simplifying to LCD but didn't think to check argument
> > > order in the call...
> > >
> > > --
> > I have tried all combinations possible... i.e. including the range / sheetname, just the sheet name, just the range, none of them and I respected the xlswrite doc for the order of the arguments. the really odd thing is that there is no error message
>
> Is there a possibility that you have the workbook open when you attempt to write to it? At least in my version of xlswrite (a bit old), it will fail to write but does not generate an error message.
> Barry
Nope, tried with wkbook open & closed. I am on a new trail now, and I suspect that there is an add in in excel that creates some issued with matlab, it is the SendToBluetooth addin and even maybe the BloombergUI addin. there is already some posts of guys who struggled to interface matlab & excel with those 2 addins on. will try this way!![]()
> "Nick" wrote in message <ku9vbj$h1u$1@newscl01ah.mathworks.com>...
> > dpb <none@non.net> wrote in message <ku8r0r$eoj$1@speranza.aioe.org>...
> > > On 8/11/2013 2:54 PM, TideMan wrote:
> > > ...
> > >
> > > > Did you check sheet A1:B2, if that is in fact a legal name for a sheet in Excel?
> > > > Because that's what you've told xlswrite the sheet name is.
> > >
> > > Good catch TM--one just presumes since the argument is a range that it's
> > > ok when in fact it likely isn't. I don't use Excel enough but I'd bet
> > > that's probably the case.
> > >
> > > I was just going to suggest OP try w/o the range just on general
> > > principles of simplifying to LCD but didn't think to check argument
> > > order in the call...
> > >
> > > --
> > I have tried all combinations possible... i.e. including the range / sheetname, just the sheet name, just the range, none of them and I respected the xlswrite doc for the order of the arguments. the really odd thing is that there is no error message
>
> Is there a possibility that you have the workbook open when you attempt to write to it? At least in my version of xlswrite (a bit old), it will fail to write but does not generate an error message.
> Barry
Nope, tried with wkbook open & closed. I am on a new trail now, and I suspect that there is an add in in excel that creates some issued with matlab, it is the SendToBluetooth addin and even maybe the BloombergUI addin. there is already some posts of guys who struggled to interface matlab & excel with those 2 addins on. will try this way!
