Cannot find project or library - Spreadsheet Journal Import not working on Excel 2007 with Windows 7 or Vista

By -
After we open the Journal Import Spreadsheet in Windows 7 or Windows Vista, it does not let us click on any buttons to create journals, etc... We get, "Compile error, Cannot find project or library".

The spreadsheet journal import, JRNL1.XLS, can be used so long as the Microsoft delivered XML library file msxml.dll exists on the environment. It does not exist with Windows 7 nor Windows Vista.
Please copy the msxml.dll file from the Windows XP computer to the workstation with Windows 7 or Windows Vista. Place the file under the windows directory where it is referenced, as follows.

--Open JRNL1.xls and then go to the VB Editor (Tools > Macro > VB Editor) or ((Developer > Visual Basic for Office 7)

--With JRNLMCRO highlighted, click Tools > Reference

There should be a reference to the Microsoft XML DLL library file (msxml.dll). Microsoft has several versions of this library (msxml2.dll / msxml3.dll / etc.) and they coexist on some computers.


NOTE:
• For Windows 7, the msxml.dll file needs to go in the C:\Windows\SysWOW64 directory.
• For Windows Vista, the msxml.dll file needs to go in the C:\Windows\System32" directory.

Comments

  1. Louis TseDecember 20, 2011 at 6:54 PM

    hi there!

    your solution works like a charm! thank you so much!!!

    ReplyDelete
  2. mukeshDecember 22, 2011 at 8:04 AM

    Hi Buddy,
    Thanks a lot for the help, I was working hard to resolve this but no one could help.....

    ReplyDelete

Post a Comment

Popular posts from this blog

Peoplesoft Error: All Processing Suspended: Restart OPRID=PS, RUNID=RUN01, PI=5000(108,503)

By mymithraa -
All Processing Suspended: Restart OPRID=PS, RUNID=RUN01, PI=5000(108,503) What is this about and what should be done? This error can occur when Application Engine programs are restartable and run via the Process Scheduler, and the last run was No Success - And an attempt re-run, rather than re-start will produce error as well The cause of this message is that previously this same AE program was run using the same OPRID=PS & RUNID=RUN01. It was not Successful on initial run, and now an attempt to RUN the same program has occurred, instead of an attempt to RESTART the original that failed. Whether this error Happened in Development??? This message happened while the Customer was in Development phase of this AE program. It could have happened when this AE was in Production as well. However, what to do would have completely different emphasis depending on if this happens in Development or Productions. During the development cycle, we would expect that this AE would have to run many tim...
Read more

Peoplesoft SFTP

By -
Image
Transferring a file using SFTP to specified target location: (Thanks to Jawahar who helped me in this article) A lot has been mentioned about sFTP support in PT 8.51. Below gives clear idea on SFTP. Are there any specific pre-requirements for using file transfer protocols? Yes. Though FTP can be used directly by giving the URL as a string to the peoplecode method, other protocols (ftps, sftp, http and https) require the URL to be passed as a URL identifier only. When an URL identifier is created, URL properties link on the page gets enabled. Users need to provide the URL properties specific to the protocol they are using on this "URL properties" page. The URL properties differ based on the protocol choosen. Once URL Identifier is ready, it can be used in any of the file attachment peoplecode methods just like the existing way.   What are the authentication methods supported for sftp? Password and Public Key authentication are supported. ...
Read more

Error: Think-time PeopleCode event (Exec), but a SQL update has occurred in the commit interval.

By -
Think-time PeopleCode event (Exec), but a SQL update has occurred in the commit interval. Faced above error after tools upgrade. Custom Application Engine (AE) program. PeopleCode step uses Exec() function with the intention of Syncronous execution of the command. When the AE runs it failed with this, or similar Think-Time error; Solution: There are Restrictions on Use of the Exec() Funtion in PeopleCode Events - and there is also a Restriction in Application Engine programs. This is based on whether the execute of the external program is Synchronous, or Asynchronous. If Asynchronous execution is selected - the execution is not 'tied' directly to the continuing execution of the running AE program, so no Think-time error results from this choice. With Synchronous execution it is different - the AE program will wait for the exectution of the command before continuing with the current process. In order for this to work with no error - a Commit has to happen before the Exec ...
Read more