Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ColInitialize has not been called!!!!!!!

Status
Not open for further replies.

RobS23

Programmer
Jun 4, 2001
161
GB
It' about time I got around to posting this!

What the heck is it and how do I stop it????

 

What program are you running? What version? When does the error occur? Give us a hint or two. Terry Broadbent
Please review faq183-874.

"The greatest obstacle to discovery is not ignorance -- it is the illusion of knowledge." - Daniel J Boorstin
 
It means some operations as copy/paste, drag and drop are not supported in some places. You can't deactivate theese messages.
John Fill
1c.bmp


ivfmd@mail.md
 

John,

Where did you get that information? How do you know that is the problem if you don't know the application being run? If you have a source for your info would you mind sharing it? Terry Broadbent
Please review faq183-874.

"The greatest obstacle to discovery is not ignorance -- it is the illusion of knowledge." - Daniel J Boorstin
 
i guess is EnterpriseManager because I had the same stupid problem John Fill
1c.bmp


ivfmd@mail.md
 
I had this when I had installed the SQL 2000 Beta on my local machine some time ago. I had SQL 2000 available on my local machine but the server was still on SQL 7. When I finally upgraded to full release SQL 2000 the problem went away. You may want to check MS TechNet also as they might have a article about it.
 
Yeah I'm talking about Eterprise Manager SQL 7.

When cutting and pasting you sometimes get this message also when I add tables to to the design view of views.

It not just that these actions are not permitted as restarting Enterprise manager clears the problem temporarily

Any Help?
 
That's exactly the behaviour I was seeing. Again upgrading to SQL 2000 cured it, but if that is not in your immediate plans, maybe try applying the latest SQL 7 Service Pack on the machine you are using EM on. MS may have addressed it. Good Luck!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top