G
Guest
I have a fairly new HP atholon based computer - bought in
January - running Windows Media Center. I also have
Windows Office Professional which I downloaded and
registered - permanently - as 1 of the "gimmees" from
going to the Vista/Office 2007 launch back in February.
I have certainly made a number of significant software
changes and setting changes since then. Including 1)
upgrading from the "as delivered" IE6 to IE7 because IE6
froze frequently; 2) installing Firefox 2.whatever.
I am aware that there may be differences between the
"Gimmee" version of Office 2007 - at least the licensing
seems to be different since the "gimmee" version can be
installed only on 1 computer. And I suppose that could be the source of my
problem. I will also admit that for a few days I did not have
the problem I am about to describe but although I try to
keep careful notes about changes, I cannot see anything
that would suggest a source of the problem.
My problem: it used to that one could create an Access
table containing an ole object as a field. Then, click on
the field, select insert object,then choose created from
file, and embed (not link) a piece of HTML. (IE7 is the default
handler, not Firefox.) Similarly, if there was already
an ole object embedded existence, one could click on the field
in the Access record open it. Doesn't work that way in
Access 2007 anymore. I have an access db I converted from
Access 2000. Everytime I try to add an object or even to
open an exsiting one, the application stalls - it goes no
place but consumes no cylces so it is not in a loop.
I then vave to go into task manager (which shows it as
non-responding) kill the app - it won't die, so I get to
report the problem to the Mothership. As I have done
dozens of times. And there is no resolution.
So I created a brand new Access database from scratch.
One simple table. It behaves lik my my
converted db. I can insert certain objects(.DOCX and
..xlsx and .rtf from wordpad ) but fails as described for .txt .html and .mht.
Any thoughts about fixing the problem, working around it
or salvaging the data I have accumulated?
January - running Windows Media Center. I also have
Windows Office Professional which I downloaded and
registered - permanently - as 1 of the "gimmees" from
going to the Vista/Office 2007 launch back in February.
I have certainly made a number of significant software
changes and setting changes since then. Including 1)
upgrading from the "as delivered" IE6 to IE7 because IE6
froze frequently; 2) installing Firefox 2.whatever.
I am aware that there may be differences between the
"Gimmee" version of Office 2007 - at least the licensing
seems to be different since the "gimmee" version can be
installed only on 1 computer. And I suppose that could be the source of my
problem. I will also admit that for a few days I did not have
the problem I am about to describe but although I try to
keep careful notes about changes, I cannot see anything
that would suggest a source of the problem.
My problem: it used to that one could create an Access
table containing an ole object as a field. Then, click on
the field, select insert object,then choose created from
file, and embed (not link) a piece of HTML. (IE7 is the default
handler, not Firefox.) Similarly, if there was already
an ole object embedded existence, one could click on the field
in the Access record open it. Doesn't work that way in
Access 2007 anymore. I have an access db I converted from
Access 2000. Everytime I try to add an object or even to
open an exsiting one, the application stalls - it goes no
place but consumes no cylces so it is not in a loop.
I then vave to go into task manager (which shows it as
non-responding) kill the app - it won't die, so I get to
report the problem to the Mothership. As I have done
dozens of times. And there is no resolution.
So I created a brand new Access database from scratch.
One simple table. It behaves lik my my
converted db. I can insert certain objects(.DOCX and
..xlsx and .rtf from wordpad ) but fails as described for .txt .html and .mht.
Any thoughts about fixing the problem, working around it
or salvaging the data I have accumulated?