I just stumbled over a (possible) bug with virtual catalogs. When you have a
category with a name that includes a "(" you are no longer able to build a
virtual catalog with this category. You can add that category to the virtual
catalog, rebuild the catalog -> open the virtual catalog -> you will get an
error message "..vb object expected....". Can someone confirm this?

regards,
Andi

[ Post a follow-up to this message ]

I can reproduce the error if including "(" in a category name.

However, it is recommended that not using special characters in category
name or product name or property name.

Similar issues are documented in KB 329681 - do not use "&" when naming
category.

Is it OK for you not using "(" in the category name?

Thanks,
Jason

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

[ Post a follow-up to this message ]

Thanks for your answer!
That's what I found in the CS2002 Docu:

Category Name
-The name must be unique.
-Do not use the characters "/," (slash) "," (comma) or " (quotation mark).
Do not use commas.
-Do not use a name that is more than 100 characters.

So no word on "do not use special characters or "(" ". The Bizdesk allows
the "(" character so we had to assume it is ok. We can live without the "("
but we have about 100 CS shops running with many, many categories in each
shop/catalog. And as our customers are using the Bizdesk to maintain their
shops we can say them do not use special characters in CategoryNames, but as
you know customers are customers and they are doing what they can do and not
what they are allowed to! ;-)

So either we need to eliminate the bug when creating Virtual Catalogs or we
need to alter the BizDesk that no spezial characters are allowed for
categorynames. Of course the first solution would be best.

Thanks,
Andi


"Jason Xu" <huanchixonline@microsoft.com> wrote in message
news:WjdNX%23FZEHA.3168@cpmsftngxa06.phx.gbl...
> I can reproduce the error if including "(" in a category name.
>
> However, it is recommended that not using special characters in category
> name or product name or property name.
>
> Similar issues are documented in KB 329681 - do not use "&" when naming
> category.
>
> Is it OK for you not using "(" in the category name?
>
> Thanks,
> Jason
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> You assume all risk for your use. © 2001 Microsoft Corporation. All rights
> reserved.

[ Post a follow-up to this message ]

If you want a fix for your problem you should open a support case with
Microsoft PSS and we can provide a fix for this problem.
I would also encourage you to evaluate the recently released Commerce Server
Feature Pack (http://www.microsoft.com/commerceserver/featurepack1/) which
provides new winforms UI  for catalog editing.


"Andreas Rathmayr" <_nospam_rathi2002@gmx.at> wrote in message
news:uCRV3ELZEHA.3480@TK2MSFTNGP11.phx.gbl...
> Thanks for your answer!
> That's what I found in the CS2002 Docu:
>
> Category Name
> -The name must be unique.
> -Do not use the characters "/," (slash) "," (comma) or " (quotation mark).
> Do not use commas.
> -Do not use a name that is more than 100 characters.
>
> So no word on "do not use special characters or "(" ". The Bizdesk allows
> the "(" character so we had to assume it is ok. We can live without the
"("
> but we have about 100 CS shops running with many, many categories in each
> shop/catalog. And as our customers are using the Bizdesk to maintain their
> shops we can say them do not use special characters in CategoryNames, but
as
> you know customers are customers and they are doing what they can do and
not
> what they are allowed to! ;-)
>
> So either we need to eliminate the bug when creating Virtual Catalogs or
we
> need to alter the BizDesk that no spezial characters are allowed for
> categorynames. Of course the first solution would be best.
>
> Thanks,
> Andi
>
>
> "Jason Xu" <huanchixonline@microsoft.com> wrote in message
> news:WjdNX%23FZEHA.3168@cpmsftngxa06.phx.gbl... 
> rights. 
rights[vbcol=seagreen] 
>
>

[ Post a follow-up to this message ]

Thanks for your message, Andi.

Since the issue can be reproduced, as Vinayak pointed out, if you would
like this issue be fixed, please open a PSS case with us.
Please call 1-800-936-5800. If this is an issue in the product, you will
not be charged.

Thanks,
Jason

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

[ Post a follow-up to this message ]

Thanks for your answers. Unfortunately is the Feature Pack not an option for
us, cause it's Winforms. Will there be a WebForms solution in the future?

"Vinayak Tadas[MSFT]" <vtadas@online.microsoft.com> wrote in message
news:%23ENq8iRZEHA.3844@TK2MSFTNGP10.phx.gbl...
> If you want a fix for your problem you should open a support case with
> Microsoft PSS and we can provide a fix for this problem.
> I would also encourage you to evaluate the recently released Commerce
Server
> Feature Pack (http://www.microsoft.com/commerceserver/featurepack1/) which
> provides new winforms UI  for catalog editing.

[ Post a follow-up to this message ]