Localized MSDE 2000

Hi,
Can anyone tell me why localized MSDEs are necessary? Does
it have anything to do with storing localized strings?
Would the English version of an MSDE instance installed on
a - let's say - Chinese version of Windows OS, have
problems storing and working with Chinese characters?
hi Lee,
"Lee" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:19cdd01c4225d$c8ee9b80$a601280a@.phx.gbl...
> Hi,
> Can anyone tell me why localized MSDEs are necessary? Does
> it have anything to do with storing localized strings?
> Would the English version of an MSDE instance installed on
> a - let's say - Chinese version of Windows OS, have
> problems storing and working with Chinese characters?
nope... Localized versions have nothing to do with data storage...
Localized versions are only versions with localized strings contained in the
localized resource libraries...
All localized versions can store unicode data and set sort order and
collations as needed...
further info about collation can be found starting at
http://msdn.microsoft.com/library/de...ar_da_1pwz.asp
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you very much for your answer.
Lee

>--Original Message--
>hi Lee,
>"Lee" <anonymous@.discussions.microsoft.com> ha scritto
nel messaggio[vbcol=seagreen]
>news:19cdd01c4225d$c8ee9b80$a601280a@.phx.gbl...
Does[vbcol=seagreen]
on
>nope... Localized versions have nothing to do with data
storage...
>Localized versions are only versions with localized
strings contained in the
>localized resource libraries...
>All localized versions can store unicode data and set
sort order and
>collations as needed...
>further info about collation can be found starting at
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/architec/8_ar_da_1pwz.asp
>hth
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://italy.mvps.org
>DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and
MSDE 2000 a visual
>interface)
>-- remove DMO to reply
>.
>

Localisation bug?

Can you tell me if this is a bug?
My browser language (Internet Explorer version 6) is set to English (United
Kingdom) [en-gb].
I have 2 reports based on the AdventureWorks2000 database.
The first report is:
SELECT PurchaseOrderID, EmployeeID, OrderDate
FROM PurchaseOrderHeader
WHERE EmployeeID = @.EmployeeID
ORDER BY OrderDate DESC
The second report is:
SELECT PurchaseOrderID, EmployeeID, OrderDate
FROM PurchaseOrderHeader
WHERE EmployeeID = @.EmployeeID AND OrderDate = @.OrderDate
I have created an ACTION link (using "Jump to Report") from the first report
to the second report which sets the parameters(@.EmployeeID & @.OrderDate)
accordingly. (ie. @.EmployeeID = Fields!EmployeeID.Value; @.OrderDate = Fields!OrderDate.Value. @.EmployeeID is type integer; @.OrderDate is type
DateTime).
Everything works as expected unless I perform the following steps:
1. Run the Report1 (deployed version) [report displays succesfully]
2. Click on the action link to jump to Report2 [report displays succesfully]
3. Click the "refresh" toolbar button (not Internet Explorer Refresh)
[ERROR!!]
The Error is:
Reporting Services Error
---
The value provided for the report parameter 'OrderDate' is not valid for
its type. (rsReportParameterTypeMismatch) Get Online Help
---
Notes:
--
1. If I run Report2 independantly, the refresh button works.
2. Everything works from VS.Net "preview" tab. It is only when deployed
that the error occurs.
3. If I set my Internet Explorer language to English(United States) [en-us]
then the error goes away!
Is this a bug?
Cheers,
JoeI've found a workaround (on this newsgroup) for this bug but it's not ideal:
Instead of using the 'Jump to Report' action you can use the 'Jump to URL'
action and specify the language setting there as follows:
=Globals!ReportServerUrl & "?/Development1/PODetail&EmployeeID=" &
Parameters!EmployeeID.Value & "&OrderDate=" & Fields!OrderDate.Value &
"&rs:ParameterLanguage=en-GB"
... and hey presto it works!
"Joe" wrote:
> Can you tell me if this is a bug?
> My browser language (Internet Explorer version 6) is set to English (United
> Kingdom) [en-gb].
> I have 2 reports based on the AdventureWorks2000 database.
> The first report is:
> SELECT PurchaseOrderID, EmployeeID, OrderDate
> FROM PurchaseOrderHeader
> WHERE EmployeeID = @.EmployeeID
> ORDER BY OrderDate DESC
> The second report is:
> SELECT PurchaseOrderID, EmployeeID, OrderDate
> FROM PurchaseOrderHeader
> WHERE EmployeeID = @.EmployeeID AND OrderDate = @.OrderDate
> I have created an ACTION link (using "Jump to Report") from the first report
> to the second report which sets the parameters(@.EmployeeID & @.OrderDate)
> accordingly. (ie. @.EmployeeID = Fields!EmployeeID.Value; @.OrderDate => Fields!OrderDate.Value. @.EmployeeID is type integer; @.OrderDate is type
> DateTime).
>
> Everything works as expected unless I perform the following steps:
> 1. Run the Report1 (deployed version) [report displays succesfully]
> 2. Click on the action link to jump to Report2 [report displays succesfully]
> 3. Click the "refresh" toolbar button (not Internet Explorer Refresh)
> [ERROR!!]
>
> The Error is:
> Reporting Services Error
> ---
> The value provided for the report parameter 'OrderDate' is not valid for
> its type. (rsReportParameterTypeMismatch) Get Online Help
> ---
>
> Notes:
> --
> 1. If I run Report2 independantly, the refresh button works.
> 2. Everything works from VS.Net "preview" tab. It is only when deployed
> that the error occurs.
> 3. If I set my Internet Explorer language to English(United States) [en-us]
> then the error goes away!
>
> Is this a bug?
>
> Cheers,
> Joe
>