Forum Home
Press F1
Thread ID: 84572	2007-11-10 20:15:00	XL Problem.	B.M. (505)	Press F1

Post ID	Timestamp	Content	User
610142	2007-11-12 22:06:00	Hi Bob Righto. I don't use macros in that way but did you notice the reference to "c:/xlstake/xlstake"? It appears there is another spreadsheet that has the UDF's. You might want to open that spreadsheet and see if there are any modules in that spreadsheet with the UDFs. If so, I would copy the UDFs from that spreadsheet into a new module of your existing spreadsheet and delete the macro worksheet - much simpler and then we can debug the UDFs (but don't do that yet). Before you do that can you post the code for the UDFs so I can see what parameters are being passed through (I also want to see what the FFJ and JC parameters etc do). And before you start making any changes you should make a copy of your existing spreadsheet in case we damage it beyond repair. Also, is the xlstate spreadsheet used by any other spreadsheets? In other words, do you have other spreadsheets that use these UDFs? Andrew	andrew93 (249)
610143	2007-11-12 22:08:00	Hi Bob You mentioned earlier that a whizz set this up for you. Is this person still around so that you can contact them? I'm thinking there may have been a reason why it was set up this way.... Andrew	andrew93 (249)
610144	2007-11-12 22:50:00	Right from the top Andrew. As it happens I did notice call (c:/xlstake/xlstake, so off I went to the route directory and lo an behold, a folder called XLstake and within a .DLL called XLstake. What the dll is all about is a mystery and I haven’t a clue what to do with it. It would appear it is an integral part of the spreadsheet though wouldn't it? I’ll get onto the UDF’s query when I get back from town but I thought the .dll may interest you in the meantime? No, I don’t know where the guy is now, but I do know the spreadsheet was created in January 2002 and has worked faultlessly up to now. A belated Y2K bug may have got it? :lol:	B.M. (505)
610145	2007-11-13 08:19:00	A belated Y2K bug may have got it? :lol: :lol: Maybe but I doubt it, if it was created in 2002. I don't think you will be able to do much with the dll file. You can create these using software such as VB6 but I don't think you can open/edit dll files (now I am getting out of my depth) without the original project file used to create the dll. Are there any other files in that directory (or sub-directory) with a suffix like vbp or something similar? Andrew	andrew93 (249)
610146	2007-11-13 18:07:00	Sorry about the delay but I got sidetracked . :rolleyes: Now, I’ve found the UDF’s and here is what they say . Note there are two Calc_Amounts, usually a bad thing?????? Calc_Amount(string) Calc_Amount() Calc_Length(String) Calc_String(String,Dividend) CopyFileTemplate(UsePubInfo) Get_Value(string,index) GetDivID(UsePubInfo) HTMLConvert(…) IsShared(OutputBook) Pop_back(string,number) Pop_front(string_number) Push_back(String,Value) That’s all they say and there is no help available . Another thing I noticed whilst crashing around is that in Edit – Link there is a reference to another workbook . I tried breaking the link and all the #REF’s appeared . Fortunately, I’d backed it up as even by reinserting the function formula nothing worked . It would seem the functions may not be available to all workbooks and one is relying on the other whether it’s open or not . :confused: All very character building so I’ll tear out some more hair today . :D	B.M. (505)
610147	2007-11-13 20:33:00	Hi Bob Now I'm getting confused......is your workbook referring to another workbook in addition to the xlstake? And are the #Ref errors still there? Did these errors only appear once you broke the links? If you reinstate the links (or restore a backup workbook) do these errors disappear? It sounds like you need someone sitting at your PC assessing this, rather then remotely.....actually I was down your last weekend (not that I was working though). Do you want to send me a copy of what you? I'd be happy to look at it. I will send you my e-mail address via PM. Andrew	andrew93 (249)
1 2