I'm currently creating a sharepoint(2013) website whilst linking it to an access database. When I link the sharepoint in the access and try to modify the fields it says it's ready only. Where can I change permissions? I tried fumbling around sharepoint for permissions however nothing seems to work also the access file itself is not read only.
You can't modify the table design of external tables using Access.
This is not a permission issue. It's just not something that Access can do.
Related
I made an access database on my desktop with several macros. I uploaded this to a network drive and when I open it, there is a message at the top that says:
"Microsoft has blocked macros from running because the source of the file is untrusted"
There is no option to allow them.
I have done some research on this and found two solutions which did not work for me. One was to look at the file properties and unblock the file. This option does not exist for me. The second was to go into the trust center settings and enable macros. They are enabled but it still will not let me use them.
Does anyone know another solution to this?
I have a report that uses a CSV file as a datasource. In Visual Studio, I can point it at the file on a share and it works. When I deploy it to the SSRS server though, it brings back an error:
The Microsoft Access database engine cannot open or write to the file 'forecast.csv'. It is already opened exclusively by another user, or you need permission to view and write its data.
Putting the file onto a share which has Everyone granted Full Control, it works. This is obviously not an acceptable security situation. I am using the following OLEDB connection string:
Provider=Microsoft.ACE.OLEDB.12.0;Data Source="\\server\share\Apps\Folder1\Folder2\DEV\SSRS\Report Foo";Mode=Read;Extended Properties="text;HDR=YES;FMT=CSVDelimited"
Of interest, another report that uses an xls file as data source works on a share that does not have Everyone Full Control access. I initially thought that it was a DFS issue but it is actually that the share needs Everyone to have Full Control. Setting the share to Full Control for the user doesn't work, it has to be Everyone
I have logged this as a bug with Microsoft
I have a quick question, is it possible to open a form created codes in access?
I have created my form but I can not find how to perceive its code in Visual Basic
Thank you for your reply
The only way I know is to export your form from access in an ASCII file, but this is not useful. Access forms are completely embedded in the mdb/accdb file and they need access executable to run. Usually you write events functions of the forms of your access project into the vba editor, but you can access properties and design details only from the design view.
I'm maintaining a VBA application in Access and a big part of this program is to make PDF's and email. I've already coded to create a PDF with PDF995, but the problem is that it keeps prompting where to save and a bunch of other questions.
Is there any solution that allows me to create PDF's in the background without prompting the user anything? I know where it needs to be saved, I know how it's going to be named, so that's not the problem.
Which Access version are you using?
In Access 2007 and above you can create PDF files out of the box, without stuff like prompting where to save.
Here's an example:
Execute Access 2007 Report and Export that Report to PDF Programmatically?
Note that in Access 2007, you have to install an add-in in order for this to work!
For Access 2003 and below, there's Steven Lebans' ReportToPDF.
i would like to distribute an access front end to some people and i want to make sure that they do not edit anything in it; however when i change the extension to ACCDR it makes all the forms and tables disappear. what settings do i have to change in order for them to be able to open forms but not view them in design view or make any changes to the forms?
The accdr extension puts your Access application into the "runtime" mode of Access, meaning the end user does not have the ability to see the built in navigation tools within Access. You would need to provide the navigation mechanism within the application yourself (for example, a startup form with links to the forms \ tables you want the users to be able to interact with).
The accdr extension hides objects from the user, but it does not prevent them from changing the file extension back to accdb and modifying your code \ objects.
To completely "lock down" the application you need to create an accde file instead. This prevents the user from being able to open a form in design view and make changes.
The following two links provide additional information about the file types and ways to deploy your application:
Intro to the Access 2007 file format
Deploy and Access 2007 Application