D
Dfalconx
Hi, on the 6/21/2006 I posted a thread seeking help for an application error
where MS Publisher would fail to start at the spash screen, due to editing a
Visio object from within publisher on a previous instance. The fix at the
time led me to regreate a new windows user account which was time consuming
and had to be done twice to get publisher to work again.
The same fault happend to me this morning again. The fix that I used this
time which worked was as follows:
Replace the "pubcmd" dat file which was 3kb with one from a health windows
user account. The replacement dat file was 2kb. The dat file is located
here:
C:\Documents and Settings\USER PROFILE\Application Data\Microsoft\Publisher
I don't know why the fault occurs. Finding the fix was from a process of
deduction. The first time this happened to me, I copied all my application
data folders into a new user profile i'd created. Publisher worked at first
and then failed to work only after I coppied over all my user settings from
the bad profile. If anyone else has a similar problem, this dat file fix
might work for you.
Duncan
where MS Publisher would fail to start at the spash screen, due to editing a
Visio object from within publisher on a previous instance. The fix at the
time led me to regreate a new windows user account which was time consuming
and had to be done twice to get publisher to work again.
The same fault happend to me this morning again. The fix that I used this
time which worked was as follows:
Replace the "pubcmd" dat file which was 3kb with one from a health windows
user account. The replacement dat file was 2kb. The dat file is located
here:
C:\Documents and Settings\USER PROFILE\Application Data\Microsoft\Publisher
I don't know why the fault occurs. Finding the fix was from a process of
deduction. The first time this happened to me, I copied all my application
data folders into a new user profile i'd created. Publisher worked at first
and then failed to work only after I coppied over all my user settings from
the bad profile. If anyone else has a similar problem, this dat file fix
might work for you.
Duncan