P. After installing MS SQL Server the server is visible within the toolbar notification area but has not started and attempts to start the application lead to a login failure.

S. Problem - SQL automatic start account problem.

1. Go to Services in Control.Administrative tools.
2. Select MSSQLSERVER, right click Properties, select Log On type tab.
3. Enter your password details OR select Local System Account button.

P. Login failure occurs when running an ASP.Net program which opens a connection to a SQL database for the first time.

S. Problem - SQL server is not configured, by default, for user account access to a database, a table, or a view. Unless you permit access to the ASPNET user account, an ASP.NET application cannot read and cannot update data in an SQL Server database.

1. Go to Enterprise Manager in Start.All Programs.Microsoft SQL Server.
2. Expand Microsoft SQL Servers, expand SQL Server Group, expand (local) Server.
3. Select Security folder, right click Logins, select New Login.
4. On General tab, enter ASP.Net user name in Name textbox (yourservername/ASPNET).
5. On Database Access tab, check boxes for databases you require access to, ensure Public is ticked in Permit in Database Role listbox for each database. Select Ok button.
6. On Database folder, for each database select Users, right click the ASPNET user account, select properties.
7. Click Permissions… button, a new dialog box appears which shows the permissions for the ASPNET user account for all objects in the database. Scroll through the list selecting the check boxes that are associated with the tables and the views that the application requires access to.
8. Click Ok twice to close both dialog boxes, then close the Enterprise Manager.

P. Many sample database base programs come with a SQL script file (filename.sql) to create the tables and stored procedures requires the use of the Query Analyzer program.

S. Problem – How to create the tables and stored procedures.

1. Go to Enterprise Manager in Start.All Programs.Microsoft SQL Server.
2. Expand Microsoft SQL Servers, expand SQL Server Group, expand (local) Server.
3. Select Databases folder, right click, select New Databases…
4. On General tab enter name of your database in the Name: textbox then select the Ok button.
5. Your Database should now be listed, close the Enterprise Manager.
6. Go to Query Analyzer in Start.All Programs.Microsoft SQL Server.
7. Set up server, SQL Server = (local), select Windows authentication button.
8. Enter your password details OR select Local System Account button.
9. Select your database using listbox on toolbar then open your script file file.open.
10. Script is now displayed, execute script F5, message should display ….successful.. message.
11. Close Query Analyzer you are now able to access your database.

P. Visual Studio provides a wizard for creating Add-ins but while developing and debugging updating can be unpredictable.

S. Problem – How to enable updates to add-in prior to code finalisation.

1. Open Visual Studio and on the start page select New Project to create the add-in.
2. Select Extensibility Projects under project type and then Visual Studio .NET Add-in under templates.
3. Enter a name for your add-in then select OK button whereupon the add-in wizard dialog will be displayed.
4. Step through the wizard recommended actions, beyond defaults deselect VSMacros tick box and select tick box for ‘Tools’ menu item.
5. After creating your add-in project open the connect.cs file within the solution explorer.
6. While developing and before your run your add-in for the first time - within the connect.cs file comment out the if ConnectMode = … statement within the OnConnection method, within the connect.cs file add the following to the OnDisconnection method (C# code shown, remember to enter the name of YourAddin on line 6):

// Dev/Debug code, get the commands collection.
Commands commands = applicationObject.Commands ;
try
 {
  // Delete the required command.
  Command command = commands.Item("YourAddin.Connect.YourAddin", -1);
  command.Delete();
 }
 catch(System.Exception)
 {
  MessageBox.Show ("Add-in OnDisconnection failure");
 }

As this code uses MessageBox add System.Windows.Forms to References in the Solution Explorer and as a Using statement within the connect.cs file, now build your code. When debugging, on the toolbar select Tools.Add-in Manager.. identify your add-in and tick the startup box, prior to closing Visual Studio reverse this action. You are now able to develop and debug your add-in remember to reverse the above code changes once you are ready to release your code.