I am running Vista, and Office 2007. In my copy of Dev Studio (7.6.5), I get errors when I attempt a PCHOLD FORMAT EXL2K BYTOC.

It's specific to BYTOC: The identical request works fine with plain EXL2K, or EXL2K FORMULA; but with BYTOC I get an error message (actually a series of them, one per tab), and then the spreadsheet opens with all the expected tabs -- but otherwise empty. Anyone else encounter this?


I opened a case, did some digging, and I think I found the cause. Using HOLD instead of PCHOLD, I found that BYTOC produces a gaggle of .xht files -- whatever.xht (the mother ship), and satelite files (a pair for each tab):

ibih0001.xht ibit0001.xht
ibih0002.xht ibit0002.xht
etc.

But when I manually opened the parent .xht file, I got the same error msgs and data deficit as with PCHOLD. Inspecting the code in the parent file, I found that half the references in the parent were wrong:

--====Boundary====
Content-Location: file:///C:/IBIT0001.XHT

"file:///C:/XBYTOC.XHT" is understood in Windows as an absolute location, in the root directory of C:. When I changed those references to relative form ...
Content-Location: ./IBIT0001.XHT
... I was able to open the spreadsheet without error messages, and the data was filled in as expected.


The particular (I almost said 'specific' -- that it's not) error message was: "The file cannot be opened because your virus scanner has detected a problem with the file." -- Clearly, the real issue is that the references point to non-existent files.

I know Vista (unlike earlier versions of Windows) protects the root directory -- at least it raises objections if you try to store files there. That may be at play -- or Excel may just be reporting this whenever it fails in opening a referenced component file (even when the real reason is that the file doesn't exist).


Has no one else run into this?

This message has been edited. Last edited by: j.gross,

Jack,

Not seen that error myself, but then I don't use Vista (I steer well clear of it to be honest).

Running similar on XP platform and I see exactly the same output (of course!) but receive no errors using standalone WF 7.6.5 but with Excel 2003.

I would concur with your suggestion that it may be down to Vista - can't see it being Excel despite its tendancy to break easily

T

Jack,

No problem running EXCEL 2007 under WinXP with WF 765.

  
-* File ByTocXL.fex
TABLE FILE CAR
SUM SALES
BY COUNTRY NOPRINT
BY CAR BY BODY
ON TABLE SET BYDISPLAY ON
ON TABLE PCHOLD FORMAT EXL2K BYTOC
END

So, I think that Vista is the problem.

one thing you may want to try if you don't know where the problem lies is see what reference libraries Excel is using and check that against the libraries used in a version that works...

for example if you are on Excel 2007 it may have different libraries as default in comparison to Excel 2003.... it's a good place to start, perhaps ask Tony A what references he is using (as it works for him) and see if you are using the same

quote:

for example if you are on Excel 2007 it may have different libraries as default in comparison to Excel 2003

How would I determine them?

I have Vista with Office 2003 and am not having any problems. I used this code and it ran fine:
TABLE FILE CAR
SUM RCOST AS 'RET_COST'
BY COUNTRY
ON TABLE PCHOLD FORMAT EXL2K BYTOC
END

Ah, yeah sorry -

if you press ALT + F11 in excel to bring up the VB/Macro screen and then go to:

Tools >References.

you will then see a list of reference libraries-many of them will have a blank check boxes next to them but the ones active will be at the top and have a check against them.

for example im using:

Visual Basic for Applications
Microsoft Excel 11.0 Object Library
Microsoft Excel 10.0 Object Library
OLE Automation

>>>>>>>>

what you wnat to do is find someone with the same set up who has no problems and ask them to telkl you what reference libraries they are using, check this aginst your sto make sure you are usign the same ones, if you aren't you should be able to find it in the list and enable it by checking its box.

as i say, it may be nothing to do with it but its a good place to check first and may provide you with a little insight as to whats going on...

Some searching turned up this solution, to turn off Norton AV's "scanning of Microsoft Office documents" feature, and that cleared the problem.

But I am still troubled by the construct "file:///c:/filename.xht" to reference a component file that is not located in the root directory.

Sounds like you cracked it, you can ignore that last post of mine, it was a shot in the dark!