Unbind Access Project from source control - ms-access

I'm using Access 2007 and the project is bound to a version control system. Everytime I open the project locally, it uses the version control connection info automatically by default. And I don't know how and where to change the connection info.
I know I can change the connection info by using "Open from Source Control". However, I'm curiouse how I can change the connection if I open it locally. And where is the version control info stored in the Access project? And How can I unbind the prject from source control?
Thanks in advance.

Related

Visual Studio - ssis project for database on server

I am using Visual Studio 2017. I am trying to create an SSIS project that works on a database I have on a server. I have the project and solution. How do I say, use this DB as source so I can create a NEW ssis package ?
Thanks
Heather F
You can create a new connection manager at either the package or project level. More details on these and their scopes are as follows.
Package Level- When the package is open in the designer, the Connection Managers window will be docked below the Control Flow. Right-click within this area go to New Connection..., highlight the OLEDB type and press Add... On the dialog that comes up, press the New... button and enter the server name that will be connected to, the authentication type (and username/password for SQL Server authentication) and the database to connect to. This database will be the initial catalog that any SQL statements will be sent to, unless they use a three part object name with the database (i.e. Database.Schema.Table). Verify the connection is successful through the Test Connection button. This connection manager is only available to the package that it is created in.
Project Level- In the Solution Explorer (if you don't see this, go to View on the top menu, then Solution Explorer), right-click the Connection Managers folder and select New Connection Manager. You can also do this from the Project drop-down on the top menu and choosing the same option. From here, you will follow the same steps as with the package level connection manager, beginning with selecting the OLEDB provider type. This connection manager will be available to all packages within the project it was created in.
Go in the Connection Managers pane and create a new connection, specific to your database type.
Then you can convert the connection to be a Project Connection(by right clicking on it).

Access Runtime 2013 app with liked tables shuts down on startup

I've written an application in Access 2013 (64-bit) that I'd like to split into front-end and back-end databases, storing the back-end on a file server where multiple machines can access the data via local instances of the front-end. None of the computers have Access installed, so I'm using Access Runtime 2013 on them.
The application runs fine when it is not split, on a single computer. As soon as I split the app into front-end/back-end files, the program opens and immediately closes on startup, with no error messages. I'm assuming that this is due to invalid links to the external data file on the first startup of the app (i.e. existing links are to folder locations on my development machine).
Has anyone experienced this problem? If so, is it due to invalid links? And, what can I do to allow the program to stay open, allowing the user to navigate to a form that I've provided in the main menu form for setting the path to the back-end file for re-linking tables?
In the load event for the menu form check if you can access the data by trying to open a recordset. If you can't, close the menu form and open your form for setting the database location. Make that there's nothing on you location setting form that is bound to the database.

IISExpress AppPool identity verification

I needed to run IISExpress under a specific identity. After going through this post how to run iisexpress app pool under a different identity I changed the processModel's username and password attributes in my \Documents\IISExpress\config\applicationhost.config file.
I would like to verify the change in my web application. Is there a way to verify?
Ultimately, what I'm after is that my security works properly using the PrincipalPermission attribute. I believe the Name property on this attribute matches the user under which IISExpress and my application are running.
Thanks in advance for your help.
IISExpress runs with current user identity and changing ProcessModel username/password won't help. Only way to run with particular identity is to launch iisexpress.exe with 'runas'.
I'm probably way too late to help, but have you tried changing your project to run with Local IIS instead of IIS Express?
Here's the way I do it (you could start in Visual Studio, but I find this more straighforward):
Launch IIS Manager with admin privilege (important that you have rights to muck with localhost)
Add a new Application Pool running with the Identity you need for your database (probably your windows account)
Create a new application on iis
point it to your project folder
assign it to the app pool you just created
In Visual Studio open your project's properties (select the project in solution explorer hit Alt-Enter or use context menu). In the Web Section, select Local IIS instead of IIS Express. No need to create virtual directory (you already did).
Now your app can open the database. As an added bonus, your project is always available to run. no need to start it from visual studio.

Distributing MS Access Application

How can I distribute a MS Access application (database) in a professional way?
I will be using NSIS to create an installation package.
I will be using a C# Application I created as a launcher for the access database file.
But when I open the access file, I am presented with the yellow security bar at the top, which warns about active content. That is not professional.
Please help!
Ms Access allows you to disable macros security just for that databae.
How?
Click the Microsoft Office Button and then click Access Options.
Click Trust Center, click Trust Center Settings, and then click Macro Settings.
There will be several options. You should click this one:
Enable all macros (not recommended, potentially dangerous code can run) Click this option to allow all macros to run.
After that you have to restart you ms access database.
The only con. about that is that you have to execute this process in every client computer. Because that setting depends on ms access instalation of the computer.
Hope it helps

Error using Microsoft Access Database to create ASP.NET website

I am creating a simple C# CMS system using a Microsoft Access database
This is my connection string in the web.config file
<add name="VirtualCMSConnectionString" connectionString="Provider=Microsoft.Jet.OLEDB.4.0; Data Source=|DataDirectory|ASPNetDB.mdb" providerName="System.Data.OleDB"/>
I have used the "Access Provider" module found here: http://blog.krisvandermast.com/UsingAccessInsteadOfSQLServerForYourASPNETApplicationServices.aspx
The problem I am having is that when I try to create a Dataset with the dataset designing I recieve an error when I try to choose the connection string for the table adapter.
Failed to open a connection to the database
"Cannot obtain provider factory for
data provider named
'System.Data.OleDb'
Check the connection and try again
Could anyone please help me on this matter.
Thanks.
Have you downloaded the .vsi, extracted it, built the SampleAccessProviders.dll and added it to your project?
Now that we have created the assembly
it's time to actually use it. Open
your Visual Studio or Visual Web
Developer Express and create a new
website. In the project you create a
new subfolder called bin. After
creation right click on it and choose
Add existing item... from the context
menu that appears. Navigate to the
place where the built assembly is. Add
it to the bin folder of the website
project. After that repeat the same
thing with the access database
(ASPNetDB.mdb) file but this time put
it in the dedicated folder App_Data
which is one of the predefined ASP.NET
2.0 subfolders.