Re: Exchange 13... No Public Folders?

In news:eFuGxon1GHA.2196@xxxxxxxxxxxxxxxxxxxx,
Dave Goldman [MSFT] <noreply@xxxxxxxxxxxxx> typed:
http://www.microsoft.com/technet/windowsserver/sharepoint/V2/default.mspx

Awww. How's that going to help me win the lottery or buy a semitropical
island paradise?


"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:eQ8xydMwGHA.4612@xxxxxxxxxxxxxxxxxxxxxxx
In news:uz4ZJcLwGHA.4876@xxxxxxxxxxxxxxxxxxxx,
John Riddle <jriddleatsignwilsongroupnyperiodcom> typed:
Thanks for you detailed response. I don't know much about SharePoint
either although I've played around enough with WebDAV that I know
I'm really not excited to learn.

I'm really not an Outlook Developer. I'm a sales person. I taught
myself in order to develop a much better CRM system than the ACT!
program that they were using when I started here.

Good on you - I don't like ACT much. Unfortunately, it does fill a
need.
It took me 6 months
to develop a great system and then when users started using it, I
worked on enhancements and new features in my spare time for another
6 months. Its a fantastic system that works better (for our
purposes) than anything I've seen on the market. There are many
thousands of lines of VBA/CDO code, hundreds and hundreds of custom
fields and a couple dozen custom forms. I also Administer the
Windows 2003/Exchange 2003 Servers that this system runs on as well
as the desktops. We have about 20 users.

I don't get paid to do any of this. I get paid to make sales. I
really don't want to have to go back and re-write the whole system.
I'm glad to hear that this will be years down the road.


And by then, you may be lying on a beach chair enjoying a tropical
drink, and thinking of ways to spend your lottery winnings. That's
my plan, anyway. Everyone needs a retirement plan.



Thanks,

John

"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:eA1sBmJuGHA.1284@xxxxxxxxxxxxxxxxxxxxxxx


In news:u0x20s$tGHA.5084@xxxxxxxxxxxxxxxxxxxx,
John Riddle <jriddleatsignwilsongroupnyperiodcom> typed:
Hello,

I saw on Slipstick.com that the next version of Exchange (Exchange
13) will not support Public Folders. The suggestion is to use
SharePoint instead.

Yes.


Well, I have developed a recruiting solution for our company which
uses Outlook 2003 and Exchange 2003. We have 3 main Public Contact
Folders and have about 100,000 contacts in them between the 3
folders (3 types of contact items). All of these public folders
have contacts that use a custom form developed with about 50
custom fields. There is a lot of vbscript behind the forms as well
as about 45,000 lines of VBA code that processes the items and
provides automation for many, many repetitive tasks that we do on
a single contact or many in a search (filter) on the Public
Folders. We additionally have several Public Calendars and a
Public Task folder with a custom task form that contains many,
many custom fields (we don't really use the items in this folder
as "task" items, but that form had more date fields/controls
built-in so it was better to use it as a template for our custom
form than any of the other standard Outlook items). If what I'm hearing
about the new version of exchange is correct,
we're going to have to move from a forms-based system built on
Outlook/Exchange to a web-based system built on
SharePoint/Exchange/Outlook? (If we can actually successfully
migrate our functionality to SharePoint)

You'll be able to see your Sharepoint data in Outlook....


I'm having a heart-attack here! I can't imagine what it will take
to migrate our system to SharePoint. It took 2 years to build as
it was. Can anyone tell me if they think that SharePoint is
capable of handling this type of functionality? Will my users have
to switch between Outlook (sending/recieving/reading mail, tasks,
calendar items, etc.) and SharePoint for Searching/Recruiting/CRM
capability and now have to use two separate applications whereas
now they simply have one interface (Outlook) ?

John

I don't think your users will notice much of a difference (although
you will). You might try posting in a Sharepoint group for more
advice,
honestly. Note as well that we're talking about something that is
years and years away from happening at this point....E12 will have
public folders (altho they won't be visible in OWA).

Myself, I'm also annoyed that PFs are going away, but then, I don't
know
much about Sharepoint yet. I may be won over.



.

Relevant Pages

  • Re: Exchange 13... No Public Folders?
    ... I'm really not an Outlook Developer. ... couple dozen custom forms. ... All of these public folders have contacts ... our functionality to SharePoint) ...
    (microsoft.public.exchange2000.clients)
  • Re: Exchange 13... No Public Folders?
    ... I'm really not an Outlook Developer. ... couple dozen custom forms. ... All of these public folders have contacts ... our functionality to SharePoint) ...
    (microsoft.public.exchange2000.clients)
  • Re: .oss files not recognized by Outlook 2007
    ... you can add them to the custom view. ... Diane Poremsky [MVP - Outlook] ... Instant search works across all item types - so you'll be limited to all ... contact view won't work on mail folders. ...
    (microsoft.public.outlook.installation)
  • Re: Exchange 13... No Public Folders?
    ... I'm really not an Outlook Developer. ... fields and a couple dozen custom forms. ... Folders and have about 100,000 contacts in them between the 3 ... migrate our functionality to SharePoint) ...
    (microsoft.public.exchange2000.clients)
  • Re: Reposting: Activities tab unable to access p.folder custom form fields
    ... The Activities tab isn't programmable and never has been. ... what version of Outlook or Exchange Activities views of Exchange public ... That's a limitation of the Exchange public folders store design and has ... > items and have access to the custom fields of those forms. ...
    (microsoft.public.outlook.contacts)
Loading