>>>>>>Have you searched for this problem - I recall reading about similar problem in MSDN VFP forum.
>>>>>
>>>>>That's what I meant when I said "Google has not given me any other ideas than those I tried"
>>>>
>>>>Right, can you post the link reference here anyway?
>>>
>>>I am not sure what link reference you are referring to, but here's a sample of my google search:
>>>
>>>https://www.google.tt/search?q=cannot+verify+the+license+for+this+product&aq=0&oq=cannot+verify+th&aqs=chrome.2.57j60j0j60l2j0.19819&sugexp=chrome,mod=14&sourceid=chrome&ie=UTF-8#hl=en&tbo=d&sclient=psy-ab&q=cannot+verify+the+license+for+this+product+office+2013&oq=cannot+verify+the+license+for+this+product+office+2013&gs_l=serp.3..0i8.8203.10249.0.16489.12.12.0.0.0.0.164.1590.0j12.12.0.les%3B..0.0...1c.1.qfxt0AuNC9A&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&bvm=bv.1357700187,d.eWU&fp=4a7657cfcf67a876&biw=1242&bih=653
>>
>>No, I meant give me a link to that MSDN thread.
>
>I didn't find anything on msdn

Hmm, I recall reading a thread on this topic in VFP forum there rather recently. I'll make a search this weekend.

I tried searching directly in MSDN but unfortunately 2013 is part of copyright.

Anyway, I found this one that remotely may be helpful
http://social.msdn.microsoft.com/Forums/en-US/visualfoxprogeneral/thread/52d153ad-f181-4064-a9ad-4511226af424