Yesterday was my first day at a new job and first day with excel in vista.

I created 3 user-defined functions, and each of them appeared to work in the
sense that they generated numbers. I was planning on testing them today.

but today I get #NAME for all of them. I have gone into the "trust center"
and enabled "trust access to the teh vba project object model". This doesn't
help.

Also, if I start to type the name of the user defined function, I see a
suggested function that has the same name below it in red. Very promising. So
I click on that. But when I click on the fx key, it doesn't prompt me for
arguments, because it no longer recognizes the function.

Any idea what's happening or how to get my user-defined functions back in
action?

Thanks.
--
Steve

Try saving the functions as an add-in (*.xlam). You have to save it in the
XLSTART folder.
C:\Users\user name\AppData\Local\Microsoft\Excel\XLStart
If the folder structure is similar to XP, your default add-in path is:
C:\Users\user name\AppData\Local\Microsoft\Add-Ins
This is where you are directed when saving an add-in. From the Add-Ins
folder, you would go back one folder (Microsoft) and go to Excel\XLStart and
save your add-in there.
--
Please rate posts so we know when we have answered your questions. Thanks.


"Steve" wrote:

Yesterday was my first day at a new job and first day with excel in vista.

I created 3 user-defined functions, and each of them appeared to work in the
sense that they generated numbers. I was planning on testing them today.

but today I get #NAME for all of them. I have gone into the "trust center"
and enabled "trust access to the teh vba project object model". This doesn't
help.

Also, if I start to type the name of the user defined function, I see a
suggested function that has the same name below it in red. Very promising. So
I click on that. But when I click on the fx key, it doesn't prompt me for
arguments, because it no longer recognizes the function.

Any idea what's happening or how to get my user-defined functions back in
action?

Thanks.
--
Steve

Forgot to mention:
You have to locate the add-in and add it to your current list of add-ins. I
think that Excel 2007 will accept the following key sequence to get to the
Add-Ins screen:
ALT, T, I
There will be a balloon that pops up telling you that you are using a 2003
shortcut and it will tell you to continue your sequence if it works. Once at
the Add-Ins screen, go to Browse, and you will be directed to the Add-Ins
folder. Go one folder up (Microsoft) and go to Excel\XLStart (where you saved
the functions if you read my previous post).
If you want to locate your functions, they are listed as User-Defined
Functions (UDF).
--
Please rate posts so we know when we have answered your questions. Thanks.


"Orion Cochrane" wrote:

Try saving the functions as an add-in (*.xlam). You have to save it in the
XLSTART folder.
C:\Users\user name\AppData\Local\Microsoft\Excel\XLStart
If the folder structure is similar to XP, your default add-in path is:
C:\Users\user name\AppData\Local\Microsoft\Add-Ins
This is where you are directed when saving an add-in. From the Add-Ins
folder, you would go back one folder (Microsoft) and go to Excel\XLStart and
save your add-in there.
--
Please rate posts so we know when we have answered your questions. Thanks.


"Steve" wrote:

Yesterday was my first day at a new job and first day with excel in vista.

I created 3 user-defined functions, and each of them appeared to work in the
sense that they generated numbers. I was planning on testing them today.

but today I get #NAME for all of them. I have gone into the "trust center"
and enabled "trust access to the teh vba project object model". This doesn't
help.

Also, if I start to type the name of the user defined function, I see a
suggested function that has the same name below it in red. Very promising. So
I click on that. But when I click on the fx key, it doesn't prompt me for
arguments, because it no longer recognizes the function.

Any idea what's happening or how to get my user-defined functions back in
action?

Thanks.
--
Steve