Not possible. The installation has been pushed down to all computer using
the same source. This particular computer was one of a dozen+ setup the
same way using Windows Server's Remote Installation Service to install
Windows XP and Windows Group Policies feature to install Office 2003.
The only way I could see the 60-day trial being installed is if I
inadvertently put in a 60 day trial code instead of the one on the OEM disk.
I this cannot be the case because I can start any office app fine and use it
without issue. It is just when I programatically try to start a new
document (Excel and Word). It happens when I do it from VBA and from other
programming sources like LabView.
Thee only thing unique about this computer is that a Software Developer uses
it. Of course I asked them if they installed anything or if they messed
with the setup in any way and they assured me the did not and there is no
possibly way their software could mess up anything because everything they
write is bug free. Scout's honor.....
> Hi, Jordan.
>
[quoted text clipped - 44 lines]
>> objActiveWkb.Application.ActiveSheet.Paste
>> objActiveWkb.Application.ActiveSheet.Cells.EntireColumn.AutoFit
Hi, Jordan.
> The only way I could see the 60-day trial being installed is if I
> inadvertently put in a 60 day trial code instead of the one on the OEM disk.
That would be incredibly difficult to guess a 60-day trial product key that
actually activated the product. Or did you have a 60-day trial product key
handy at the time?
> I this cannot be the case because I can start any office app fine and use it
> without issue. It is just when I programatically try to start a new document
> (Excel and Word).
It can happen, but only if more than one version of Office is installed. If the
last version installed were a 60-day license that has expired, programmatically
opening the application would give you the error message from the last version
installed, yet opening the application from the Start Menu or a shortcut that
specifically names the path to an unexpired version would make everything look
peachy keen. Hence, two different outcomes from what appears to be the same
application opening.
> Thee only thing unique about this computer is that a Software Developer uses
> it.
That could be the problem. ;-)
More likely, the installation partially failed or some new application was
installed on the computer afterwards that trashed part of the Office
installation. You can try re-registering the Automation files, but check the KB
article on the following Web page first for some troubleshooting tips:
http://support.microsoft.com/kb/q244264/
If that doesn't help, re-register these files (located in C:\Windows\System32):
Asyncfilt.dll
Oleaut32.dll
Olepro32.dll
Stdole2.tlb
Stole32.tlb
Click Windows Start, and then click Run. Use the following command:
Regsvr32.EXE "C:\Windows\System32\Asyncfilt.dll"
. . . and so on for the other files.
If that doesn't work, uninstall and reinstall the Office applications.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info.
> Not possible. The installation has been pushed down to all computer using the
> same source. This particular computer was one of a dozen+ setup the same way
[quoted text clipped - 60 lines]
>>> objActiveWkb.Application.ActiveSheet.Paste
>>> objActiveWkb.Application.ActiveSheet.Cells.EntireColumn.AutoFit