I have an Access 2003 project that I am trying to open in Access 2007. The first action I take is a Macro with the action Minimize, followed by executing a module that opens my starting form. This is so the user only see the opening form and not any of the access tables. However when I open the project in Access 2007, the minimize does not work, the tables show. What am I doing wrong?
Two things to try:
Ensure macros are enabled in the trust center (under access options in the main menu) in Access 2007
Ensure your minimize macro is named AutoExec in Access 2003
Related
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
whenever we open up a particular database, it opens to a table and then we have to open up the report we work from. For security reasons, we'd like the database to open to a particular report rather than the default table. Is there a way to change the database's behavior to open a record by default? Perhaps through a command line switch? In this particular case, we'd want to open a report named "01 Dashboard" by default upon opening the database.
Also note, we are on Windows 10, running Office 365.
Thank you.
Create an AutoExec macro that opens the report.
Or edit the existing one (or the VBA code it calls), if it really is a table that is automatically opened, and not a form in datasheet view.
Can anyone tell me what this prompt means? I really know nothing about Access nor have much experience with VBA. My goal is to view the VBA code from an Access forms.
I open the .accdb file.
I open the Form Designer
I go to the Design ribbon, and click View Code
Visual Studio opens up and I get the following "db2 password" prompt:
Does this have anything to do with IBM's DB2 product? or is it just a misleading prompt?
Does this prompt mean that the developer has password protected the source code, but not the .accdb file itself?
You're trying to access a VBA code project which is password protected. Nothing to do with IBM. They've just named their project db2
If you right click on a project > Properties you get this dialog. Someone has filled it out.
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 have an old Access 2000 app (I don't do much Access dev these days) that a client is trying to run in Access 2007. It runs fine for the most part, except the forms do not behave as-designed when they are called/instantiated, etc: Access 2007 puts every new form inside a "Tab" of sorts, which is causing confusion on the part of the end user (modal forms they can't "tab out of," etc., seems to be the kind of thing they are mentioning).
It was designed as a typical MDI app, and ran fine that way for years. Is there a way to override Access 2007 "taking over" the forms handling?
Yes. Set Document Window Options to Overlapping Windows, then save the database (which should persist it to subsequent runs).
From here:
By default, Microsoft Office Access
2007 databases display as tabbed
documents. To use windowed documents,
click the Microsoft Office Button
Button image, and then click Access
Options. In the Access Options dialog
box, click Current Database and, under
Document Window Options, click
Overlapping Windows.
More information about transitioning to Access 2007 here as well.