Member Avatar for pritesh2010

hello every one
i had created one application front end as vb.net and back end is Access 2003. after this i had created a setup of that application. it perfectly work on my computer but when i am installing setup on my friends computer it install and run time it gives the error of connection string.
so how to solve the problem of connection string after making setup. i want to make application like if i run on any computer it should be install and work properly.
please help me it's urgent.

  • 2 Contributors
  • 1 Reply
  • 133 Views
  • 7 Hours Discussion Span
  • Latest Post Latest Post by kvprajapati

Dani AI

Generated

Notes for — the error is almost always environmental, not VB.NET. Common causes: the installed connection string points to a file path that does not exist on the target PC, the OLE DB provider (Jet/ACE) is missing or has a 32/64-bit mismatch, or the installed folder denies write access (Access needs to create an .ldb lock file). is correct that the connection string lives in the config, but changing it manually after every install is fragile. A more robust approach is a DSN-less string with a relative path (use the |DataDirectory| substitution) or have the installer write the correct path into the deployed .config.

Example DSN-less strings (store in app.config or update at install):

Provider=Microsoft.Jet.OLEDB.4.0;Data Source=|DataDirectory|\MyDatabase.mdb;User Id=admin;Password=;

Provider=Microsoft.ACE.OLEDB.12.0;Data Source=|DataDirectory|\MyDatabase.accdb;Persist Security Info=False;

Deployment gotchas to resolve now: compile the app for x86 if using Jet (Jet is 32-bit only). If moving to ACE (for .accdb or 64-bit), confirm the ACE redistributable on the target machine; mixed Office bitness can block ACE installs. Do not install a writable .mdb into "Program Files" — place it in ProgramData or a user-writable folder and have the installer set folder permissions so the .ldb lock can be created.

Quick troubleshooting checklist for a failing install: read the exact exception text, confirm the Data Source path exists in the installed .config, check installed OLE DB providers, try forcing the EXE to x86, and test the provider with a .udl file on the target machine. Connection-string examples and provider details are documented at ConnectionStrings.com and the .NET |DataDirectory| substitution is described by Microsoft here.

Member Avatar for kvprajapati

>please help me it's urgent.

Please read the rules before posting again - http://www.daniweb.com/forums/thread78223.html and rules.

>connection string

Open applicationname.config and change the connection string once an application is installed.

Edited by kvprajapati because: n/a
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.