help files in English (QA)

Dear fellows,
From my workstation I've got QA and its help files, in spanish. I'd like to
have in english and so I would avoid to use Terminal Server (against
production servers) for consult that info in English...
Is there any way for to change this?
Thanks a lot for any input or advice,
--
Please post DDL, DCL and DML statements as well as any error message in
order to understand better your request. It''s hard to provide information
without seeing the code. location: Alicante (ES)The support files for Books Online are stored in the following location:
C:\Program Files\Microsoft SQL Server\80\Tools\Books
The link is as follows:
C:\WINDOWS\hh.exe "C:\Program Files\Microsoft SQL
Server\80\Tools\Books\SQL80.col"
You could create a new folder like the following and copy the files from
another workstation that had an Engligh install:
C:\Program Files\Microsoft SQL Server\80\Tools\Books_EN
Once done, create a new shortcut on your desktop for the following:
C:\WINDOWS\hh.exe "C:\Program Files\Microsoft SQL
Server\80\Tools\Books_EN\SQL80.col"
I would expect that only one version of BOL can be linked with QA, EM and
the other client tools, so you would need to access the Engligh verison of
the documentation using the above shortcut.
Also, there is MSDN.com
"Enric" <vtam13@.terra.es.(donotspam)> wrote in message
news:E90A46EB-EBFD-4967-ADF9-FD5030B0F1A7@.microsoft.com...
> Dear fellows,
> From my workstation I've got QA and its help files, in spanish. I'd like
> to
> have in english and so I would avoid to use Terminal Server (against
> production servers) for consult that info in English...
> Is there any way for to change this?
> Thanks a lot for any input or advice,
> --
> Please post DDL, DCL and DML statements as well as any error message in
> order to understand better your request. It''s hard to provide information
> without seeing the code. location: Alicante (ES)|||hi JT,
Have done but not successful results. my workstaton is in spanish. Maybe
that's the reason. I have 'Archivos de programa' instead of 'Program Files'
--
Please post DDL, DCL and DML statements as well as any error message in
order to understand better your request. It''s hard to provide information
without seeing the code. location: Alicante (ES)
"JT" wrote:

> The support files for Books Online are stored in the following location:
> C:\Program Files\Microsoft SQL Server\80\Tools\Books
> The link is as follows:
> C:\WINDOWS\hh.exe "C:\Program Files\Microsoft SQL
> Server\80\Tools\Books\SQL80.col"
> You could create a new folder like the following and copy the files from
> another workstation that had an Engligh install:
> C:\Program Files\Microsoft SQL Server\80\Tools\Books_EN
> Once done, create a new shortcut on your desktop for the following:
> C:\WINDOWS\hh.exe "C:\Program Files\Microsoft SQL
> Server\80\Tools\Books_EN\SQL80.col"
> I would expect that only one version of BOL can be linked with QA, EM and
> the other client tools, so you would need to access the Engligh verison of
> the documentation using the above shortcut.
> Also, there is MSDN.com
> "Enric" <vtam13@.terra.es.(donotspam)> wrote in message
> news:E90A46EB-EBFD-4967-ADF9-FD5030B0F1A7@.microsoft.com...
>
>|||I don't see why an Engligh (.chm) help file can't be opened; adjust the
folder path to the files as needed. The Engligh characterset is part of a
Spanish language install of Windows.
"Enric" <vtam13@.terra.es.(donotspam)> wrote in message
news:577F1495-5E28-4201-A399-B901E8A13D0C@.microsoft.com...
> hi JT,
> Have done but not successful results. my workstaton is in spanish. Maybe
> that's the reason. I have 'Archivos de programa' instead of 'Program
> Files'
> --
> Please post DDL, DCL and DML statements as well as any error message in
> order to understand better your request. It''s hard to provide information
> without seeing the code. location: Alicante (ES)
>
> "JT" wrote:
>

Help - setup Sql Server 2000 on server on network

Hello -
I have a VB6 application that is hooked up to a Sql Server database on my
workstation computer. I will be distributing this application and have to
install Sql Server 2000 on a server. I have never set up Sql Server on a
network server before. Please tell me if the following steps are correct:
1. Set up Windows 2000 Server operating system on the machine (they want me
to use a separate computer from our other servers).
2. Connect to the network.
3. Install Sql Server 2000 on the machine.
4. Copy the MDF and LDF files from my workstation computer to Sql Server
2000 on the server into the ../MSSQL/Data file.
According to my logic (or lack thereof, as the case may be), my application
should be able to connect to this database from any computer in the
organization via a connection string (which is located in my application)
like the following:
"Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=MyDatabase;Data
Source=NewServerThatSqlServerWasJustInstalledOn"
Any comments and suggestions will be greatly appreciated!
--
SandySandy,
It basically sounds like you're trying to move a SQL database from one
instance of SQL Server to another and then connect to that new instance via
your client application. That is not an issue as long as the client
application has the necessary connection information/string to the new
instance and the network connectivity is present. However, there may be
some issues with security as any logins will not be transfered because they
are stored in the Master system database and not in the end-user database
(only contains the db users). As such you may want to view the Microsoft KB
article #246133.
HTH
Jerry
"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:57C7E2E5-6906-4B47-BE22-71983B3A6DF8@.microsoft.com...
> Hello -
> I have a VB6 application that is hooked up to a Sql Server database on my
> workstation computer. I will be distributing this application and have to
> install Sql Server 2000 on a server. I have never set up Sql Server on a
> network server before. Please tell me if the following steps are correct:
> 1. Set up Windows 2000 Server operating system on the machine (they want
> me
> to use a separate computer from our other servers).
> 2. Connect to the network.
> 3. Install Sql Server 2000 on the machine.
> 4. Copy the MDF and LDF files from my workstation computer to Sql Server
> 2000 on the server into the ../MSSQL/Data file.
> According to my logic (or lack thereof, as the case may be), my
> application
> should be able to connect to this database from any computer in the
> organization via a connection string (which is located in my application)
> like the following:
> "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
> Info=False;Initial Catalog=MyDatabase;Data
> Source=NewServerThatSqlServerWasJustInstalledOn"
> Any comments and suggestions will be greatly appreciated!
> --
> Sandy|||Hi Jerry -
Thanks for your response! You are correct; that's essentially what I want
to do. I just wanted to make sure I had my steps correct and that I wasn't
forgetting anything.
In looking at my "list" again, I did forget that I have to be sure to put
the log on a separate drive on the server.
Anything else I may have overlooked?
Thanks for bringing the security issue to my attention!
--
Sandy
"Jerry Spivey" wrote:
> Sandy,
> It basically sounds like you're trying to move a SQL database from one
> instance of SQL Server to another and then connect to that new instance via
> your client application. That is not an issue as long as the client
> application has the necessary connection information/string to the new
> instance and the network connectivity is present. However, there may be
> some issues with security as any logins will not be transfered because they
> are stored in the Master system database and not in the end-user database
> (only contains the db users). As such you may want to view the Microsoft KB
> article #246133.
> HTH
> Jerry
> "Sandy" <Sandy@.discussions.microsoft.com> wrote in message
> news:57C7E2E5-6906-4B47-BE22-71983B3A6DF8@.microsoft.com...
> > Hello -
> >
> > I have a VB6 application that is hooked up to a Sql Server database on my
> > workstation computer. I will be distributing this application and have to
> > install Sql Server 2000 on a server. I have never set up Sql Server on a
> > network server before. Please tell me if the following steps are correct:
> >
> > 1. Set up Windows 2000 Server operating system on the machine (they want
> > me
> > to use a separate computer from our other servers).
> >
> > 2. Connect to the network.
> >
> > 3. Install Sql Server 2000 on the machine.
> >
> > 4. Copy the MDF and LDF files from my workstation computer to Sql Server
> > 2000 on the server into the ../MSSQL/Data file.
> >
> > According to my logic (or lack thereof, as the case may be), my
> > application
> > should be able to connect to this database from any computer in the
> > organization via a connection string (which is located in my application)
> > like the following:
> >
> > "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
> > Info=False;Initial Catalog=MyDatabase;Data
> > Source=NewServerThatSqlServerWasJustInstalledOn"
> >
> > Any comments and suggestions will be greatly appreciated!
> > --
> > Sandy
>
>