Compile error: sub or function not defined

[matze]

hi there,

once again i've got a problem.
i want to export a single sheet of my workbook into a new workbook. therefore i've got the following code:

sheets("Channel").Copy
ActiveWorkbook.SaveAs fileName:="C:\test.xls"
ActiveWorkbook.Close

but if i run that sub, i get this error:

Compile error:
Sub or function not defined!


furthermore vba marks the line

call WriteManifoldResults

as i am a bloody beginner i would guess the error occurs because of some functions linked to the sheet i want to export. so my questions basicly are:

1) is it because of the links leading to the sheet?
2) how can i solve this problem

thank you very much
i'd be absolutly thankful for every little help.

cheers

matthias

 

[wigi]

Did you surround this piece:

sheets("Channel").Copy
ActiveWorkbook.SaveAs fileName:="C:\test.xls"
ActiveWorkbook.Close

with a name for the procedure?

Sub [I]MyProcedure[/I]()
sheets("Channel").Copy
ActiveWorkbook.SaveAs fileName:="C:\test.xls"
ActiveWorkbook.Close
End Sub

 

[Yard]

Looks like your code is trying to call a procedure called WriteManifoldResults which doesn't exist in your project. Either:

- delete the line which calls it (bearing in mind this could have knock-on effects)
or
- re-establish the WriteManifoldResults procedure in your project so it gets called successfully

HTH

 

[matze]

well, actually the programme works perfectly if i - in example - save the whole workbook under a new name or export not the whole sheet but one of its charts. usually the "Call Writemanifold"-line works without problems. that's why i guess it has to do with the links. strange excel.

 

[Yard]

So maybe the code which is calling the Writemanifold sub is not in the same workbook as the Writemanifold itself?

As per wigi's question, you haven't explained where your code sits so it's a bit hard to figure out why it's going wrong.

I'm not convinced this is some "strange" behaviour on Excel's part.....

 

[wigi]

I'm not convinced this is some "strange" behaviour on Excel's part.....

Must definitely be a bug in Excel