Preparing Websites with Active Content for Announced Browser Changes

If you use ActiveX controls like Macromedia Flash on your page, as my brother does on http://www.otomnekadar.com, with the Internet Explorer updates, the users will not be able to interact with them unless they "Click to Activate" them...

There is a solution for this on Adobe site :
Adobe site

The link seems like it will not be there forever, so here is
the link to the JavaScript files
you would need...

Since we struggled to find this, thought might help others

Business Data Catalog in Sharepoint 2007

This was something I was tryingto do with data connections, and dataviews in FrontPage.

How cool is this...

Microsoft SharePoint Products and Technologies Team Blog : Business Data Catalog

Microsoft SharePoint 2007 > Rolling up information in SharePoint Sites

Here are two long-waited parts in the new version, that answers "How can I see all my documents in a gazillion workspaces?", Well, not gazillion :) , but if you have a handful, that would work:

Microsoft SharePoint Products and Technologies Team Blog : Rolling up information in SharePoint Sites

Delighted to see this coming up.

I need to check if it is possible to roll them up vertically in one single list, lol, and yes, without touching the database ;)

FitzBlog : Please Stay Out Of The Database!!!

I am a Sharepoint Object Model fan...

I find it very well designed, and thought.

A little old posting, but worth to check:
FitzBlog : Please Stay Out Of The Database!!!

Even I touched the database "sparingly" in crisis cases, like for version upgrade after a disaster, I agree with most of the points there. The fact that there is a caching layer between sharepoint and the database makes it even riskier.

However, I also think that, ideally, for an enterprise product, it should either be NOT possible at all, or not be an issue. SQL server is capable of handling locks, isn't it?

I posted my comments there, I was wondering what would be the best way to determine weather a 3rd party web part uses direct database approach...

Introduction to Upcoming SharePoint Products and Technologies

Hi,

Mike Fitzmaurice gives an overview of the technologies that will release within Microsoft Windows SharePoint Services (version 3) and Microsoft Office SharePoint Server 2007, with an eye toward pointing out areas with specific developer opportunities.

If you are involved in, or thinking about getting involved, you must see this...

What's Coming in WSS "v3.0"

What's Coming in WSS "v3.0"

A very cool list compiled by Gene Kraybill, and posted on Dustin Miller's blog...

Some links are broken, but still valuable information out there...

Sharepoint Bloggers

I have asked, and was accepted to http://www.sharepointblogs.com/, which is a more specialized blog for sharepoint community.

At this time, I will keep posting the items there, and refer to it here...

Duray AKAR

Windows sharepoint services site directory

There will be a site diretory in the upcoming version in WSS, but I think it is one of the biggesst whoos in the WSS2.0, that there is no site directory...

Sharepoint Portal Server has a sophisticated one, but WSS lacks a built in site directory...

So I developed my own webpart:


Displays the site hierarchy for the current user, points out the current site, shows the siblings, sister sites, and parent site...

Pretty simple, isn't it ?

Can share the code or CAB if anyone is interested.

SharePoint List of Bloggers

Mark Kruger compiled the most inclusive SharePoint List of Bloggers I have came across...

I asked to be in :) maybe he will include my blog there ...

Moving data between workspaces

Posted this on sharepoint university:
Moving data between workspaces

If I get some interest, I will share the code to do it ...

Microsoft CRM 3.0

I attended a CIO technical event in Ft Lauderdale, and learned about the new version of Microsoft CRM.

It has gone far beyond since version 1.2.

I am exploring my options on how to get it implemented in my work place...
hopefully it would integrate a lot of separate pieces that we have, and become the boiler plate for all the applications we use. We are a "service oriented" company, so we should fit well in the target market for the product.

10 things that I like most about it is:

1) Integrated into Outlook
2) Actually looks and feels like OUTLOOK, not like a monster living in there
3) Has online / offline as well as mobile capabilities, thanks to Outlook
4) Utilizes SQL Reporting Services
5) Has a SQL Server back-end, UNLIKE Outlook
6) Can import/export data from your existing CRM systems
7) Can host your existing .Net assemblies
8) Has a REALLY VERY SIMPLE and at the same time FLEXIBLE workflow implementation
9) Uses ENTITIES, which are CUSTOMIZABLE, and RELATIONAL
10) Integrates with Sharepoint


Things that I did NOT like about it :

1) Try to get a pricing ! I mean how complicated can that be? Is it worth NOT publishing the price online? Is it even more complicated than SQL server pricing ? :)
2) Demo labs are 30 minutes. It takes 5 minutes to setup the environment, so you got a FULL 25 MINUTES to play with it :)

MSDN and TechNET labs are 90 minutes, so why this one wouldn't be ? I don't know.

Hopefully I will learn a lot more know about it shortly.