Re: **Urgent** New Edit in Datasheet error occurring on proven WSS

Tech-Archive recommends: Speed Up your PC by fixing your registry

We got WSS V3 and Office 2K3 Prof. clients. Datasheets views have been lost
in some of them (those upgraded with Office 2K3 SP3), but not in others.

I think upgrading WSS to V3 won't be a solution to the problem, since it
depends of Office 2003 client configurations and upgrade level.

Regards

"Jack_Feeman" wrote:

We have over 1200 users so our upgrade plans for Office 2007 are not in the
near future since the user experience will change quite extensively, we will
need to train the userbase first. However, we will be upgrading to WSS v3 so
hopefully we wont run into that issue.

"JonathanD" wrote:

We actually upgraded our WSS 2.0 to SP3 and that caused the issue on the
client machines running Office 2K3. Since we only have a few people that use
the functionality I decided to attempt some client-based fixes. Last night
we found that if you upgrade to Office 2K7 the issue is no longer there. So
as our temporary fix, this is our solution ...

"Jack_Feeman" wrote:

I wonder if anyone out there has installed Office 2k3 SP3 and is not
experiencing the data*** lockout. We do not have that problem but we have
not installed SP3 yet either (and I do not think we will.....yet). Can you
use system restore to back out of the SP3 on a machine to see if that
restores the data*** functionality?
Thanks Jack

"rookie" wrote:

On Oct 1, 12:50 pm, Jack_Feeman <JackFee...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
I didn't see any resolution yet for this issue, so....

I had a problem with SPD 2007 being used with Office 2203 and WSS2.0. The
answer I got worked fine and solved the issue.

So if your issue is caused by this incompatibility, try this solution
provided by Cornelius J. van Dyk:

http://www.cjvandyk.com/blog/Lists/Posts/Post.aspx?ID=103

Thanks Jack



"Arthur Pounder" wrote:
Hello,
This issue has been reported by several organisaitons. As I understand it,
Microsoft are working on a fix for this issue.

A

"bsr1031" wrote:

WSSSP3being applied to our servers was the culprit for us. We managed to
recreate the issue in a couple of test environments as well. The datagrid
functionality works fine untilWSSSP3is applied to the server.

"Mike Walsh" wrote:

Do you know whether in your case theSP3was applied to clients; servers
(theWSS2.0server); or both ?

Mike Walsh

bsr1031 wrote:
We've beenfollowingthis thread and have finally fixed the problem at our
company. We ended up doing a repair of the WSS2 installation and then an
uninstall and reinstall of the .Net Frameworks. After that the datagrid was
working fine again. Some clients had to delete their temporary internet
files afterwards, others did not. Hope this helps those who are still having
issues.

"gocat2005" wrote:

Our Sharepoint system has been in use for 2 years - fine.

Today when users try to Edit inDatasheetusing Office 2003 or 2007 Pro this
error isdisplayed:

"Thelistisdisplayedin Standardview. ItcannotbedisplayedinData***
viewforoneormoreof thefollowingreasons: Adatasheetcomponent
compatible with Windows SharePoint Services is not installed, your browser
does not support ActiveX controls, or support for ActiveX controls is
disabled."

We have loads of users screaming about this. Is it to do with Office 2003SP3?- Hide quoted text -

- Show quoted text -

Since we rarely log on to our WSS 2.0, I just installed SP3 yesterday
and am having the same complaints from users, that they can no longer
"Edit in Data***". I checked in the OWS file that Dan mentions
above and we already have that RenderActiveX function included. Has
there been any update from Microsoft or any other resolution that
anybody has found? Any help is greatly appreciated as our users are
freaking out ...

Thanks!


.

Quantcast