• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums User Experience Lawson Add-Ins for Microsoft Office

Self contained GL40 JE upload template

 2 Replies
 0 Subscribed to this topic
 1 Subscribed to this forum
Sort:
Author
Messages
Display Name
Basic Member
Posts: 17
Basic Member
2/5/2014 6:08 PM
Our finance department uses the GL40 upload template that was available on the mylawson download sight years ago.

I am familiar with the typical requirements for URL/user id to be remembered between uses for Add-ins, however this template writes LoginCurr and LoginHist files to the C:\Program Files\Lawson Software\Common folder not the \Add-ins folder and doesn't use or require a LoginDir folder, though out of desparation I have added one anyway. 

The issue I am having is only with one PC, all the other PCs using this template have the URL saved each time the file is used. 

On this PC if Add-ins is launched normally through Excel it recalls the URL and userid without fail (again, the /Add-ins/LoginDir folder). When the self contained template is used, no such luck. It doesn't write the files to the /common folder as it should.

I have explicitly given the userid full access to the folder and the full path above it. It just isn't writing those files. I also added the MRU key to the registry (Current User) and populated the last server string, etc manually, no luck.

The only difference I can find between the working and non-working PC is that the non-working PC is a 64bit version of Windows7, the others are all 32bit Windows7. All have Excel 2007 SP3. We use Add-ins version 9.0.3.1380.

Does anyone know what needs to be modified to make this work on a 64bit machine? Different VB references? XML version?

Short of that, any suggestions for a troubleshooting procedure? I'm stuck.

Thanks
The.Sam.Groves
Veteran Member
Posts: 89
Veteran Member
2/5/2014 8:30 PM
Have you tried copying the required files from the Common folder from a working PC into the Common folder of the problem PC?

My recollection is that Windows Vista and forward required special permissions in order to be able to create files in the Programs Folder and it's subdirectories. Given the self-contained template is a macro and not a full-blown program on it's own, instead of triggering the request for permission to create its files properly on the 64-bit machine, it could just be silently failing.

You might also want to double check the 'other' Program Files folder.

Remember 64-bit Windows reserves the normal Program Files folder for 64-bit apps and Program files (x86) for 32-bit apps. So you if you were speaking literally concering the file loctations in your question, those may not be the correct folders.

Good luck!
Display Name
Basic Member
Posts: 17
Basic Member
2/6/2014 1:03 PM
I think that's it! I knew of the two folders and have been looking in the x86 folders but didn't make the connection that the vb is writing to program files but needs to be x86 program files. Thanks!