Database Search

match allmatch any Look in all areasLook in current areas Check all datesPrevious dayPrevious 3 daysPrevious weekPrevious fortnightPrevious monthPrevious 2 monthsPrevious 3 monthsPrevious half-yearPrevious year

TechHome

• Access 2000 Advanced DML Transactions
• Access Recordset to CSV File UDF
• Access RunCommand Constants
• ACCESS Table or Query Exists
• Access to Excel via SQL
• Access Visible Problem
• Adding Fields to an Existing Access Table
• Advanced DML Transactions
• Advanced SQL in the Jet 4.0 Provider Example
• Another OLE with Access Example
• Automating Access Tutorial
• Check if Access Table Exists
• Commit Rollback Begin Trans Updatebatch
• Control Access Forms
• Count Access Records
• Csv to Access
• Dealing with ACCESS 97 Field Types
• execute a macro in Access
• Execute a Public function in Access
• Export Access Report in Choice of Formats
• Export MDB to Flat File
• Find Read and Insert Data in Access
• Gather ACCESS Table and Column Information Into Excel
• Get Access Version That Created MDB File
• Get Column Data From an Access Database
• Get Record Count
• How to Use the OpenTable method
• Launch Access Macro from Commandline
• Loop thru a recordset in Access
• Office 2003 Macro Security Issue
• OLE and Access
• OLE Import a table into Access
• OLE Import Table into Access
• Open Access DB with DAO
• Pack an Access Database
• Query and Export Data from Microsoft Access
• Read Write Delete Tables from Access DB
• Repair MDB
• Retrieve Data in Access
• SQL UPDATE Fails with Access
• UDF to Return Record Count
• Updating Table From Filtered Recordset
• Ways to Get Data from and Access file without Access installed

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

Office 2003 Macro Security Issue

---

Much publicized, but a real annoyance to programmers and legacy databases. Both Access and Excel, if not set to the lowest security level will pop-up messages about security when trying to load earlier versions of those products [I got called about an Access97 MDB, and updating to the Jet 8 patch].

Admins and small-business owners, overwhelmed with viruses and MS security patches are often reluctant to set security low or off.

The attached addresses that issue with an Access.Application Object - I'll have more in a bit about any problems with ADO and the Jet Provider; and Excel is a whole different can of worms. stan

; Office 2000
; overriding Security to load earlier versions
;
;/////////////////////////////////////////////////
cMDB = "C:\test\mdb97.mdb"
If ! FileExist(cMDB) Then Exit

oAcc = CreateObject("Access.Application")
If oAcc.Version >= 10 Then oAcc.AutomationSecurity = 1 ;msoAutomationSecurityLow
oAcc.Visible = @True
oAcc.OpenCurrentDatabase(cMDB) 
If oAcc.CurrentProject.FullName <> ""  
     oACc.UserControl = @True
Else
     oAcc.Quit()
     Message("Database Open Failed",cMDB)
EndIf

oAcc=0

---

Article ID:   W16598

File Created: 2005:02:18:12:21:34

Last Updated: 2005:02:18:12:21:34