In case anyone is interested in testing this out, here is the finished code.
This works in Access 2003.
Option Compare Database
Private Sub Detail_Print(Cancel As Integer, PrintCount As Integer)
For i = 0 To 2700 Step 5
For j = 0 To 1800 Step 5
x0 = 3 * (i / 2700) - 2
y0...
I recently found out about the graphics functionality that can be utilized during the paint event of a report. So I wanted to stress test it. I realize this is far outside the realm of what Access was designed for, but I'm still getting some weird behavior that I'd like to fix if possible...
Yep. That's the solution I went for. It was just weird that this behavior occurred.
I guess we can just chalk it up to an Access bug. (could be a pain in some cases)
Sorry but what exactly is a DSN? I see many references to it on the web and an abstract definition, but I'm not sure what it is if it's not simply the account I'm using to link a table.
I have two linked ODBC tables in my access applications. If I link them both with the same account, they work fine.
If I link them each with a different account, when I view one, it will work fine. When I try to view the other, it will give an ODBC call failed.
Regardless of which one I view...
I have a two dimensional array of strings:
Dim testArray(3, 3) as string
I need to pass this to a function.
I've tried every combination of syntax possible for passing this to a function to no avail.
Function analyzeCell(ByRef currentArray(,) as String) gives "Expected:)"
Function...
When a report loads, I go to Tools -> Office Links -> Analyze It with Microsoft Office Excel
Choosing this option launches excel with an excel version of the report.
And I think:
DoCmd.RunCommand acCmdOutputToExcel could work.. but the problem is it has no argument for which object to export...
Access 2003 (11.8321.8333) SP3
Oh well. I'll just allow Tools access for everyone for now. (Most of the users are computer literate enough that I need not worry)
Later on I'll come back and create "analyze with excel" functionality of my own so that Tools doesn't need to be enabled for anyone...
I did test your method. Exactly as you said.
I created a function that did a CurrentDb.Properties("AllowFullMenus") = True
I made an autoexec macro that runs this function.
I even put a msgbox after the property set to make sure the function was being called and it was.
This was no different...
Unfortunately this method isn't any different since even after the Autoexec runs and it authenticates the user and sets the menu property accordingly, no effect will be seen until restarting the database.
What I wanted to do was allow manager-level users to go "analyze this report with excel"...
I see that if I manually change the properties in the immediates window as you said, then it indeed toggles them. But the effects aren't seen until the next time the user launches the database.
I was actually hoping to toggle the property (not just a startup property) while the database was...
I found some code online to do this but nothing seems to work.
When I execute the line of code: CurrentDb.Properties("AllowFullMenus") = True, I get no errors. So I know the property exists.
Yet it doesn't do anything when I set it. I'm trying to allow/disallow full menus based on user's...