I am currently developing a big winforms project that connects to a SQL Server 2005 database.
The idea is that the application will be deployed on random clients whenever needed. These clients have neither SQL Server installed, nor is there a server to provide a central database. The only option is to include the database file with the deploy.
Now, I've searched all around the internet on how to do this. I just can't seem to connect to the database-file from my deployed version. Is there something special that needs to be done?
How do you deploy changes to a database? Is there something you can run to compare the two versions and create a script to do this? I've heard about the DTS package (now DTSX I believe) but am not sure how to set one up. If anyone could point me to an article or something that might clear things up, it would be greatly appreciated. Thank you!
I have an application being developed in VS 2005 using SQL Express. I've built up some new roles and have several users pre-populated that I'd like to deploy to a shared hosting evironment. The problem is that I seem to keep getting: Database 'd:hostingmemberasangaApp_DataASPNETDB.mdf' already exists. Choose a different database name.Cannot attach the file 'd:hostingmember 2agilitysite1App_DataASPNETDB.MDF' as database 'ASPNETDB'. I saw another post with a similar issue, but that resolution has not seemed to help. Can anybody give me insights as to where the "asanga" is coming from? That might help me diagnose the issue. Thanks in advance
Greetings,I've been looking around all morning and can't seem to find a good answer on this so I thought I'd post a message here.I'm using the recommended practice of keeping the ASPNETDB.MDF data separate from my site data. (I have my site data located in separate databases but still keep them in the App_Data directory.)I'm using SQL Server 2005 Express on a Server 2003 box and I've implemented scheduled backups on the databases in the Sql Server.The questions I'm having are:1. Why isn't the ASPNETDB.MDF database getting attached to the server? Is it using User Instances?2. If it is using User Instance then isn't this degrading performance? If so, how to force it to not use User Instance?3. If User Instance is how it is supposed to work then how are we supposed to do a full backup of the ASPNETDB.MDF database if it isn't attached in the server? (xcopy doesn't seem to work on User Instances because of the dreaded "is being used by another process" error.)Any recommendations, advice, links, or answers to my questions would be greatly appreciated.
This question has been asked before, with vague responses I'm using Visual Web Developer 2005 Express, SQL Server 2005 Express and SQL Server Management Studio Express. When I create an application with Login controls, VWD automaticlly creates a ASPENTDB.MDF security database. I also create my own database for my application e.g. abc.mdf. In other words, I have two databases. However, my hosting company supports only one database. What do I (we) do? I have seen articles on: aspnet_regsql . Does this create a new database with all the security features of ASPNETDB.MDF built into my new database i.e. abc.mdf? (A) If yes, how do you run it with SQL Server Managment Studio Express? It sounds silly, but I need instructions here please ... Also, do you run this against abc.mdf or do you use it create abc.mdf? (B) If not, how do you achieve a single database scenario? I'm sure this is a very common deployment question, which is very confusing for most of us hobbyists that want to deploy their web applications
HiI'm using sqlexpress on development machine and on client server. I'm building a webapp using membership and role provided for asp. In web.config I have definet membership provider and role provider to point to my database.After web site deployment I get allways message : Failed to update database "c:appapp.MDF" because the database is read-only, and I'm forced to apply rights for ASPNET. More than that somethimes I must re-register users.I have tried to modify in web.config with <remove name="LocalSqlServer"/> <add name="LocalSqlServer"...> but I get errors if I try to design my dataset file:"Cannot get web application service".TIAPaul
I have developed a database in Visual Studio 2005 (c#) ,using SQL Express as my database, on my local machine and deployed it to a different machine where it is being used in a live environment. No problems.
However, I have continued developing the application on my local machine and have made numerous additions to the structure of the database (on the development machine).
My question...How do I go about deploying the new database structure to the live machine without losing the live data?
I am trying to deploy a SQL Server Express database to a remote SQL Server 2005 host. I was planning to copy and paste the data from my local tables to the remote tables using Management Studio Express but my ISP (NTL) appears to be blocking port 1433 and preventing me from getting a connection to the remote database. Will an upgrade to SQL Server 2005 Developer Edition help me? I understand that it has a Backup & Restore Wizard but how does this work? Does it rely on a remote connection and will it fall foul of the NTL port blocking? Or, can the file that the Backup stage produces be copied into the web-based MSSQL Manager, that my web host provides, to restore to the remote database? Any help would be much appreciated.
Hi, I work with a large team developing ASP.NET application that has a large database with over 50 complex stored procedures. It is proving more and more difficult and time consuming to centralise the development and update of the database changes and I was wondering if there were any best practises/tools that could be recommended. I have looked on the web for good articles and haven't found anything difinitive (except that Team Foundation Server is the way forward).. A brief background to the current process is that everyone develops on the same database, and then updates the stored procedure scripts in source safe (manually). Then when we do a new release someone builds a script of all the database updates and runs it. There are issues related to developers updating there stored procedures over other peoples and other concurrency. I am looking to move all the developers to start using local databases so that there work only effects them, but then this brings up problems of keeping all the local databases up to date whenever they get the latest source code. The only way I currently see is to build a database update program, that will run and update to the latest version. Surely this must be a common issue? Anyone have any good ideas/concepts? Also our setup is Visual Studio 2005, SQL Server 2005 and Source Safe 2005. Cheers, Andrew Thomas
I have searched hi and low for hours within the product and online - I cannot find how to have SQL 2005 produce a script to automatically repeat the creation of a database role I have tedious manually created.
I have tried "script object as, create to,<>" - single-liners are produced - no details. More single line results from "<Database>, All Tasks, Generate Scripts".
Am I missing something or is this a bug?
€¦also to note after review blogs and other sources the use of the SQL2005 methods related to security and new schema objects - I feel€¦ dreadfully wrong - what is claimed feels like hype, unsupported by examples and usage cases feels like we better just make all automated processes sysadmin; I know learning curves can be strong but I am not this green or that stupid - where are the DOCS/training materials?
I deployed my application to my newly installed xp pro laptop
The prerequisites are installed
Now that I want to testdrive my database application I get this error:
An attempt to attach an auto-named database file c:/program files........................MyDB.mdf failed. A database with the same name exists, or specified file can not be opened, or it is located on UNC share.
I want to create deployment for MS SQL 2005 Express database, that creates database, tables and inserts data. I have made a similar with VisualStudio 2003 and MSDN
I am trying to write a short application within which I would like to embed a SQL Server Express database, all of which would be deployed via ClickOnce through a web site. The installation process seems to be working without trouble, including installation of the .NET Framework 2.0 and SQL Server Express 2005.
When the application launches on the new machine, however, I get a big Microsoft .NET Framework "Unhandled exception" error dialog box that indicates the database already exists and that the database file could not be attached. I am working with a clean virtual machine that I know has never had the database installed on it.
I fear I am overlooking something quite straightforward, but since this is the first time I have ever attempted to build a data-bound application, I am not sure where I am going wrong.
Perhaps the source of the problem, or a related problem, might be revealed even when I run the application in debug mode from within Visual Studio. I can run the application once, but if I try to run it again, I get an error when I try to open the database connection that is similar in content (database already exists...could not attach). I can run the SSEUtil and detach the database and then run the application again in debug mode and it works no problem (the first time!).
Lastly, if I install the application on the machine on which it was developed and make sure the database is detached, it will run without any trouble (even repeatedly). But, on a new blank machine, there is no database listed that matches my database name, so I cannot try to detach anything!?
Well, I'm been trying to resolve my problems through searching previous post, but I'm starting to go around in circles. This is what my problem is: Originally, I created a SSIS package using windows authentication. Once I completed the work, I wanted to change the connection to SQL Server authentication and use xml configuration for deployment.
First problem: I edit the xml file, but can't use the connection I double clicked the Connection Manager connection and changed the log on from Windows to SQL Server. Password would not save, so, I read about what most posts have been about and I can go into the SIS menu, choose Package Configurations and create a xml file with the name of my connection manager.
Then, I exit the package and go into the xml file and enter the password=XXXX; stuff right after the user Id. When I load the package, the connection does not load?? Shouldn't the package pick-up the password now that I have entered it? I used note pad to edit the xml. If I go into note pad, I can see the edit. If I use SSIS package config to view the file, I don't see the password. I'm also having sql agent task problems, but I think I will be able to solve this if I can get the package to run with the password in the design mode. Can anyone help me with this?
I hope the answer is as simple as the question -- but after reading all the documentation I could find (understand?) and a lot of posts here, I'm no closer to achieving the goal.
I have a Visual C# app, DAYTRACKER, developed in VS2005. It uses a database with several tables constructed using SQL Server 2005 Developer Edition.
I want to deploy the app plus the database plus SQL Express to another machine, to be used by a single user (the administrator) with no need for network connectivity of any kind.
What I have so far is: 1. The application is successfully deployed from a CD-ROM, having used the Publish process within VS2005, and opens on the new machine -- without database connectivity, however. 2. SQL Express is successfully deployed (it deployed as a 'prerequisite' when I went through the Publish process in VS2005) 3. I manually copied the database's .mdf and .mdl files, using SQL Server Managers 'Copy Database' function, then transferred the copies to the new machine into the ..MSSQL.1MSSQLdata folder (where they appear along with the master.mdg, mastlog.ldf etc files)
Now, the DAYTRACKER application's DAYTRACKERConnectionString under 'Settings' in the VS2005 studio reads 'Data Source=DELL3;Initial Catalog=DayTracker;Integrated Security=True' (which are the appropriate parameters for the machine, DELL3, on which I wrote the program.)
The problem, of course, is that SQL Express on the new machine doesn't connect the application to the database. When I go to the 'SQL Server Configuration Manager' and go to the 'SQL Server 2005 Services' and double-click on the 'SQL Server (SQLEXPRESS)' icon (the service is running) and the user is logged on using 'Local System Account'. Under the 'Service' tab the Host Name is 'MUSIC' (which is the name of the new machine I've installed the app onto -- which of course is not the name - DELL3 - that the app's connection string is expecting). Under the 'Advanced' tab, I've tried correcting the name of the Startup Parameters default .mdf and .mdl entries to ..DayTracker.mdf and ..DayTracker_log.mdl, but the server won't start up after I make the changes.
What I'm hoping for: a step-by-step way of doing this type of deployment, preferable getting it all onto one CD-ROM, and installing it on the new machine so that it all works seamlessly from the start, not requiring any 'tweaking' of the SQLServer Express settings by the end-user.
But I'll take pretty much anything that fixes the specific db connectivity problem I've described.
I'm trying to test my ASP.NET application. Everything is working to the point of getting to my login page to open. When I try to login I receive and error that the database does not exist or access is denied. I used the developer version of SQL Server to create the database and installed the MSDE on my test PC. Then I copied the mdf and ldf files to the new PC. Is there something else I should be doing? Or any suggestions?
I created a sql database on my development machine for my .net app. There are whole brunch of tables and stored procedures. Now I'm at the point to test my app on integration environment, instead of recreating each table and stored procedure, is there an efficient way to promote them. (note I use both MSDE version on both machine)
Hi all,I am doing a project that involved with the big volume of data to beuploaded to the SQL server. Due to the limitation at my employer'ssite, I couldn't have the bulk admin right. I am looking at thecommand BCP and wonder if there is any copyright issues if I were touse BCP and to deploy the command?Thanx.
I want install the project in client side .. In installation time i want to access the my server .. How i can make the setup file to access the internet.. please help me.....
I tried to deploy a package to production and failed miserably. The error is pretty simple "Format of the initialization string does not conform to specification". Trouble is, I opened my source on the production machine, generated a new connection string from a new connection manager and guess what, the string comes out EXACTLY the same as the one my package is set to point to at runtime. so, where do I start?
some general stuff. There are ADO and OLEDB connection in the package. Each gets its connection string from a variable. the variable is set in a script task which pulls the data out of an encryped sql server column. when the connection string is displayed via a simple message box, it is exactly what I want i to be, e.g. Data Source=a.b.c.d;User ID=A_USER;password=password;Initial Catalog=a_database;Provider=SQLNCLI.1;Auto Translate=False;
I am guessing that it must be a setting or option on the SQL Servers themselfs, something in its configuration as otherwise the strings are identical so there must be something in the way that one SQl server is not set up to allow connections from another?
I'm working through Ch 3 of "SQL Server 2005 Reporting Services Step by Step" by Stacia Misner, published by Microsoft Press, but I can't get the example report in Ch3 to deploy. I get a long error message, which says this:
TITLE: Microsoft Report Designer ------------------------------
A connection could not be made to the report server http://localhost/ReportServer.
Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'. The request failed with the error message: -- <html> <head> <title> SQL Server Reporting Services </title><meta name="Generator" content="Microsoft SQL Server Reporting Services 9.00.2047.00" /> <meta name="HTTP Status" content="500" /> <meta name="ProductLocaleID" content="9" /> <meta name="CountryLocaleID" content="1033" /> <meta name="StackTrace" content=" at Microsoft.ReportingServices.Diagnostics.RSConfiguration.Load() at Microsoft.ReportingServices.Diagnostics.RSConfiguration.Construct(String configFileName) at Microsoft.ReportingServices.Diagnostics.RSConfiguration..ctor(String configFileName, String location) at Microsoft.ReportingServices.Diagnostics.RSConfigurationManager..ctor(String configFileName, String configLocation) at Microsoft.ReportingServices.Library.Global.get_ConfigurationManager() at Microsoft.ReportingServices.WebServer.Global.StartApp() at Microsoft.ReportingServices.WebServer.Global.Application_BeginRequest(Object sender, EventArgs e)" /> <style> BODY {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE: 8pt; COLOR:black} H1 {FONT-FAMILY:Verdana; FONT-WEIGHT:700; FONT-SIZE:15pt} LI {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE:8pt; DISPLAY:inline} .ProductInfo {FONT-FAMILY:Verdana; FONT-WEIGHT:bold; FONT-SIZE: 8pt; COLOR:gray} A:link {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC; TEXT-DECORATION:none} A:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#FF3300; TEXT-DECORATION:underline} A:visited {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC; TEXT-DECORATION:none} A:visited:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; color:#FF3300; TEXT-DECORATION:underline}
</style> </head><body bgcolor="white"> <h1> Reporting Services Error<hr width="100%" size="1" color="silver" /> </h1><ul> <li>The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError) </li><ul> <li>Access to the path 'C:Program FilesMicrosoft SQL ServerMSSQL.3Reporting ServicesReportServerRSReportServer.config' is denied.</li> </ul> </ul><hr width="100%" size="1" color="silver" /><span class="ProductInfo">SQL Server Reporting Services</span> </body> </html> --. (Microsoft.ReportingServices.Designer)
I'm attempting to deploy CLR Stored Procedures from Visual Studio 2005.
I have a VS Database project with stored procedures for all of the tables in our database. (I would really like to keep everything together in 1 DLL), everything seems fine except...
I keep receiving the following error when attempting to deploy to SQL Server:
Error 1 Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
After some experimentation I have determined that its because the DLL is too large: 1.8 mb. (I also have a larger one).
I have looked through various documentation sources but have found none concerning this problem other than specifing something aboug a 100ms execution timeout (not sure if this is the same).
Deployment works if I trim down the size of the DLL (i.e., remove procedures from the solution)
Is there anyway to deploy large DLLs to SQL Server without having to break them up? If so, where is the setting to allow a longer timeout period for deployment?
Have my first .NET app deployed to remote host and configured successfully, except for one thing: can't figure out how to export my SSE tables to the SQL server database on the remote server. I tried SQL Server Management Studio Express ... with that, I can access the remote database, but can't access the local database file I produced with VSWDE. What is the appropriate tool to use to export tables from a local SSE database file to a remote SQL Server 2005?
I am trying to add membership to my site. i use visual web developer and the set controls. i.e. login etc. I also used the asp web config tool which is where my test users are. Everything works locally. but when i upload it and try to log on I get this error message: Server Error in '/' Application.
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:
[SqlException (0x80131904): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +735043 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +820 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84 System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197 System.Web.Security.SqlMembershipProvider.GetPasswordWithFormat(String username, Boolean updateLastLoginActivityDate, Int32& status, String& password, Int32& passwordFormat, String& passwordSalt, Int32& failedPasswordAttemptCount, Int32& failedPasswordAnswerAttemptCount, Boolean& isApproved, DateTime& lastLoginDate, DateTime& lastActivityDate) +1121 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved, String& salt, Int32& passwordFormat) +105 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved) +42 System.Web.Security.SqlMembershipProvider.ValidateUser(String username, String password) +83 System.Web.UI.WebControls.Login.OnAuthenticate(AuthenticateEventArgs e) +160 System.Web.UI.WebControls.Login.AttemptLogin() +105 System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e) +99 System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +35 System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +115 System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +163 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102 Can anyone out ther please help me with this. thanksNick
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210
I have a dev machine with VS2005Pro, WinXPSP2. I create a web site with authentication built with the ASP.Net Configuration Tool in VS2005.
The site, login and all other functionality are fine when tested on the dev machine.
I use copy web site to 'deploy' the site to a W2003R2 server. The authentication process doesn't recognize the password. All other web functionality is fine. With SSMSE I can see that the request is actually being processed by SS2005E.
Is this likely to be an encryption problem due to differing machine keys or something similar? What is the recommended approach to moving ASPNETDB from the dev machine to a server?
Hi. I created an app on my laptop and wish to deploy it to a server. I followed the steps to release the project and I copied the files over to the server. I'm getting an access denied or server does not exist error message. I went into the code behind pages to change the connection string but it still doesn't work. I think it has something to do with the SQL Server name. It's just local. The person that installed it did not change the name. In enterprise manager, it looks like this. (local) (Windows NT) Should the connection string be SERVER/(local) ? Is there a default name I'm not aware of? Any help would be greatly appreciated. Thanks!
Here is the error message:
Server Error in '/' Application. --------------------------------------------------------------------------------
SQL Server does not exist or access denied. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
hi everyone. i've recently upgraded to ASP.NET 2.0 and have successfully created a web application using the 2.0 membership provider. everything is working GREAT... ...until it's time to deploy! for the past 2 days i have been stuck trying to figure out why my app cannot connect to my SQL Server 2005 database. i am plagued by the: "login failed for user 'NT AUTHORITY/NETWORK SERVICE'" error. the database is aspnetdb.mdf located in the app_data folder of my web application. the "LocalSqlServer" connection string name is used for connecting to the database (using the "attach" menthod steps taken so far: installed vs2005 on the target server, opened the project, connected to the database and added the "NT AUTHORITY/NETWORK SERVICE" user as a db owner to the aspnetdb.mdf database installed SQL Server 2005 Management Studio Express to try to accomplish the same thing as through vs2005 gave the NT AUTHORITY/NETWORK SERVICE account full access to the folder where the web application resides. attempted to create a custom connection string to attach the database and connect using an SQL user instead of a windows user, but "attaching" an MDF file seems to only work with integrated security. attempted to attach the database using the Management Studio Express and added a SQL user as the db owner. but SQL can't find the database even when it's attached. i've deleted, rebooted, uninstalled, reinstalled, recopied, etc. several times with no luck. one thing that i find very peculiar: on the target server, when i open the WSAT through vs2005 it shows 0 users, even though there ARE some in the database when i run the app on in development environment. in this situation, i try to log in to the application and the login page returns a "user not found" error. after returning to the WSAT and creating a new user, i try to log in again and get login failed for NT AUTHORITY/NETWORK SERVICE again. can someone PLEASE help me. it just doesn't seem like it should be this difficult. the new membership provider in 2.0 is really easy to use...how could it be so difficult to deploy?? PLEASE PLEASE PLEASE help. thanks in advance!
I hv developed a client server application that uses Access Xp ( adp file) as front end and SQL Server 2000 as database. Inside the vba code i hv extensively made use of sql dmo library objects. For the program to work properly i am forced to install Sql server client tools especially (enterprise manager) on end users workstation which is something i am not happy with. Whithout SQL client tools installed Access pops up an error like "Can't create activex object".
I googled that issue and gathered informations stating that some dll's file must be installed for SQL dmo to work smoothly in a VB application and i guess that same also stands for Access vba since they are almost quiet the same.
In my application setup package i hv included these below dll's and they hv been set to be loaded in application directory as following but the problem still remains.
