Hi Leandro,

Make sure that you include the machine name in the server text box with Specify. If you are using SQL 2005 Express your server should be {MACHINE_NAME}\{SERVER_NAME} and if you kept the default, your server name will be "SQLExpress". If you try to access your database and you cannot connect, it is likely that your firewall is blocking access. You can create an exception for SQL Server so it will get through your firewall. This is how you do it if you are using the Windows Firewall, if you are using a different firewall you will need to follow the documentation for it to open up access to SQL Server. Go through the start menu and open up the control panel. Open up Windows Security Center and then select to manage security settings for Windows Firewall. When the Windows Firewall settings are displayed, select the Exceptions tab. Next, click "Add Program..." and then select the "Browse..." button. For SQL Server 2005 Express, you will need to select the program located (default) at: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlsrvr.exe. Click Open and then OK a few times to finish. Then try to open Specify again. I will try to write up the procedure this afternoon to open the firewall and will post a link when it is finished.

CJ

Hi Grady,
Thanks for the fast answer.
I turned off the firewall temporarilly, but didn't have success.

I suppose I am mistaken something.
When do I have to "tell" Specify in machine B to access the database on machine A?

When the Specify starts, there are some fields. All of them are empty (I have no database attached). In the "Server" field, I putted "\\name-of-machineA\SQLEXPRESS" and in the "database" field I putted "Peixes_Mzusp" (is the name of the .mdf database). The sa and password account I putted those from MachineA, but I kept getting the connection error.

Are those procedure I made correct?

Cheers, Leandro

You should first attach the database on the server machine and then use the client machine for access. Try that and let me know how it works.

Hi Grady,
I already attached the database on the server machine. How do I access this from the client? Do I just need to login at \\machine\SQLEXPRESS or do I need to attach again?
Do I need to have SQL Express installed on the client too (or just Specify)?

You just enter in your credentials and then select login. You do not need to attach on the client machine. You may want to make sure that you have SQL Server 2005 Express set up to accept external connections. If needed, use the SQL Server Configuration manager and expand "SQL Server 2005 Network Configuration" and then click "Protocols for SQLExpress". Enable the protocols in the right pane and restart your server. Then try to log in from your client machine.

OK, I changed "SQL Server 2005 Network Configuration" and now all "Protocols for SQLExpress" are enabled. But...no connection yet.
Maybe I am writing something wrong to connect to the server. How is the "sintax" to fill in the Server field? Two bars + name of the machine + one bar + name of SQL Server? Like "\\LEANDRO\SQLEXPRESS" ?

You do not need to include the leading double bars. It should just be LEANDRO\SQLEXPRESS

Hi Grady,
Well, I quit. I guess the SQL Server doesn't like me.
I will keep using Specify with MSDE in a standalone workstation.
Maybe I will post funniest topics next time (like how to design our labels).

Thanks a lot and I appreciate your help.
Cheers,

Leandro,

Don't give up yet, you are very close! I will write up a procedure that will show you how to set everything up. I will post before I leave today.

CJ

I have written up the procedure to configure SQL Server 2005 Express to accept remote connections, it is located at: http://www.specifysoftware.org/specifyforums/procedures/sql2005RemoteConfig

The procedure to open your firewall for SQL 2000 and SQL 2005 is located at: http://www.specifysoftware.org/specifyforums/procedures/sqlFirewall

Let me know if I missed anything!

CJ

Hi Grady,
After some time, I finally got it! Now Specify is accessed by several stations. I instaled it on a machine running "Windows 2000 Server" with "SQL Server 2000".
Thank you so much by the help.