SysExpert
asked on
"Invalid or nonexistant document" when recompilng a blank template with jst a a script library, R 6.5.5
This appears to happen to me in any template or DB that as a script library. It stops after pass1, says compilation is OK, and then show the message
"Invalid or nonexistant document"
and never gets to pass 2. If I remove the script library, it works fine.
Any suggestions, on how to get it to complete pass 2 ?
tested on a blank DB,
The script library only has
Option Public
Option Explicit
in the Options and nothing else. No actual code.
Thanks !
"Invalid or nonexistant document"
and never gets to pass 2. If I remove the script library, it works fine.
Any suggestions, on how to get it to complete pass 2 ?
tested on a blank DB,
The script library only has
Option Public
Option Explicit
in the Options and nothing else. No actual code.
Thanks !
You already tried to close down Notes and restart? Or a complete reboot? And a Recompile all LotusScript?
Maybe the compiler doesn't consider an empty library to be a real thing. Add one statement to the Initialize-event, like just
Dim i As Integer
Dim i As Integer
ASKER
Tried all of the above. No difference so far. Still the same message.
Tried on a second machine. Same thing.
Try it yourself and see if this also happens to you.
Create an NSF from the blank template.
Run recompile. - No errors.
Add a library in the shared code with just a line or two of code ad recompile again.
Tried on a second machine. Same thing.
Try it yourself and see if this also happens to you.
Create an NSF from the blank template.
Run recompile. - No errors.
Add a library in the shared code with just a line or two of code ad recompile again.
No forms, just the one library?? It compiles correctly. R6.0.3 here.
Hi SysExpert,
Tested 6.5.4, no problems with either option Explicit or Option Declare
Regards!
Tested 6.5.4, no problems with either option Explicit or Option Declare
Regards!
ASKER
Strange. I tested again today with a fresh instal lof R 6.5.5 on a test machine. Still happens.
I'll test with 6.5.4 soon.
Thanks !
I'll test with 6.5.4 soon.
Thanks !
Are you sure your blank.nsf is really empty? Or maybe the icon is missing. :)
ASKER
I tested after a fresh R 6.5.5 install that had r 6.5.4 previosuly, that was uninstalled, and removed NOes directory , Notes.ini and all references in the registry.
So the Blank DB was based on the Blank template that is installed by default.
Again. Recompile works on the blank DB Before I add anything to the script library.
As soon as I add
option explcit
It stops working, finisj=hed only pass 1, and gives the message. Even though it says it sucessfuly compiled all scripts.
So the Blank DB was based on the Blank template that is installed by default.
Again. Recompile works on the blank DB Before I add anything to the script library.
As soon as I add
option explcit
It stops working, finisj=hed only pass 1, and gives the message. Even though it says it sucessfuly compiled all scripts.
Fascinating... You tested this on other PC's as well? Can you send us the zipped database?
ASKER
I have sent the DB's to both of you zipped.
please test and let me know.
please test and let me know.
ASKER
I am going to have to resend since the ACL was not set for designer.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Very Strange.
DId any of you use R 6.5.5 ?
I am going to install a clean R 6.5.4 to test.
On 3 different machines with R 6.5.5 ( one a clean install ) this happened.
Thanks for your feedback !
DId any of you use R 6.5.5 ?
I am going to install a clean R 6.5.4 to test.
On 3 different machines with R 6.5.5 ( one a clean install ) this happened.
Thanks for your feedback !
No, I'm running 6.5.3. But have had odd errors in designer after an upgrade... usually meant that I renamed bookmarks, desktop and delete cache to have Notes rebuild. So a fresh install might do the trick.
ASKER
OK.
R 6.5.5 was a clean - fresh install on my third machine. Still happens.
I uninstalled it and put in R 6.5.4 and the problem disappeared. so it seems to be an R 6.5.5 designer bug
I will open a ticket with IBM.
Thanks for all of your help.
R 6.5.5 was a clean - fresh install on my third machine. Still happens.
I uninstalled it and put in R 6.5.4 and the problem disappeared. so it seems to be an R 6.5.5 designer bug
I will open a ticket with IBM.
Thanks for all of your help.
Don't you think it's a waste of time/money? Signalling IBM that the error is there is a good thing, but check R7 first before putting too much into this. I think it's more of an academical nature...
ASKER
SInce we are not ready to upgrade to R 7 yet ( as I am sure there a lots of people who are also waiting ), then I think it is best to report it and get it resolved.
The majority of my users are still R5.
The majority of my users are still R5.
ASKER
OK, this issues was already reported
The issue you report is associated with SPR# MMAY6K9RFQ, and it is fixed in:
6.5.6
7.0.1
And it is available in a CCH (Cumulative Client Hotfix) for 6.5.5 Notes client on w32 platform
So since I solved it myself. This Q, can be closed.
The issue you report is associated with SPR# MMAY6K9RFQ, and it is fixed in:
6.5.6
7.0.1
And it is available in a CCH (Cumulative Client Hotfix) for 6.5.5 Notes client on w32 platform
So since I solved it myself. This Q, can be closed.
So don't install R7.0.0 ;)
It's a touch disappointing to take time to assist a fellow EE, only to have them say, "oh, I solved it myself.." ;(
It makes you think: why respond in this question, there is nothing to be gained. I think you're right, it was my first thought too.
ASKER
Well I searched IBM site for recompile and nothing relevant came up. As you all know, the IBM site still has it's own issues.
I Think that the fact that there is a Hot fix out there that I and others were not aware of, speaks for itself.
Sorry for wasting your time ( and Mine ) I spent lots of hours trying to resolve this also !
I Think that the fact that there is a Hot fix out there that I and others were not aware of, speaks for itself.
Sorry for wasting your time ( and Mine ) I spent lots of hours trying to resolve this also !
I'm sorry, too. Didn't mean to be short with you, I am glad you found the answer, boy that must have been annoying!
sjef.. just read your comments..
Now, what we did prove in this discussion is that the problem you were experiencing was/is unique to 6.5.5, and that it doesn't occur on any of the other platforms. Both of us took time to test your database and narrow down the problem for you. I do believe a "thank you" is in order, if nothing else.
The question now, is this valuable information for anyone else? And should the question be kept?
Now, what we did prove in this discussion is that the problem you were experiencing was/is unique to 6.5.5, and that it doesn't occur on any of the other platforms. Both of us took time to test your database and narrow down the problem for you. I do believe a "thank you" is in order, if nothing else.
The question now, is this valuable information for anyone else? And should the question be kept?
ASKER
I did thank everyone
Comment from SysExpert
Date: 04/03/2006 10:56AM EST
Your Comment
OK.
R 6.5.5 was a clean - fresh install on my third machine. Still happens.
I uninstalled it and put in R 6.5.4 and the problem disappeared. so it seems to be an R 6.5.5 designer bug
I will open a ticket with IBM.
Thanks for all of your help.
-------------
But I certainly am willing to do so again, and I really do appreciate your efforts in narrowing down the issue for me.
Comment from SysExpert
Date: 04/03/2006 10:56AM EST
Your Comment
OK.
R 6.5.5 was a clean - fresh install on my third machine. Still happens.
I uninstalled it and put in R 6.5.4 and the problem disappeared. so it seems to be an R 6.5.5 designer bug
I will open a ticket with IBM.
Thanks for all of your help.
-------------
But I certainly am willing to do so again, and I really do appreciate your efforts in narrowing down the issue for me.