MartyConnelly
martyconnelly at shaw.ca
Wed May 26 14:52:44 CDT 2004
At some places I know, the users and developers would be outside the Net
Admin's door with pitchforks and torches.
Even places like DND run completely seperate secure systems.
Here is one way around Access Security macros via vbs but I suppose this
has been disabled.
However you should be able to run this from Access 97, calling an
Access 2003 app with macro security set to off by changing this one line.
Set AcApp = CreateObject("Access.Application.11")
Works on my machine with both versions installed.
Const cDatabaseToOpen = "C:\<FileToOpen>.mdb"
On Error Resume Next
Dim AcApp as object
Set AcApp = CreateObject("Access.Application")
If AcApp.Version >= 10 Then
AcApp.AutomationSecurity = 1 ' msoAutomationSecurityLow
End If
AcApp.Visible = True
AcApp.OpenCurrentDatabase cDatabaseToOpen
If AcApp.CurrentProject.FullName <> "" Then
AcApp.UserControl = True
Else
AcApp.Quit
MsgBox "Failed to open '" & cDatabaseToOpen & "'."
End If
Welz wrote:
> Charlotte is correct. The IT people see Access as a program that
> creates files just like Notepad creates files. Since they installed
> Access 97, I have permission to use it to create mdb/mde files.
>
> Winzip or its ilk are not permitted. It is not possible to create a
> shortcut on the desktop, shell to DOS, create ODBC connections or
> install any software. It is also not possible to email certain files
> nor to access an email account from outside the offices except through
> Terminal Services, with no ability to save data to a disk at a remote
> machine. Only a few laptop users have access to a floppy drive at all
> and it is not possible for me to log on to the LAN with any laptop I
> bring on site. Any attempt to install any software on a laptop
> allowed on the system or on the terminal server is blocked and fails.
> If I want to email myself an Access application I'm working on, I
> currently have to break it into several dozen files with a few
> forms/reports/modules in each, rename them as doc files and reassemble
> the objects into a container offsite. This tactic does not work with
> large graphic files though. I've seen an mda at Dev's mvps.org site
> that purports to do this but I'm not sure I can get it up and running
> in the target environment. For this reason I'm looking for some
> straight forward File I/O code that will do the trick.
>
> They are starting to move to A2K3 and I've converted the application
> but my users cannot run it yet and they have not addressed self
> signing the 'macros' in Access. When they do, the jig may be up.
>
> Ciao
> Jürgen Welz
> Edmonton, Alberta
> jwelz at hotmail.com
>
>
>
>
>
>> From: "Charlotte Foust" <cfoust at infostatsystems.com>
>>
>> Arthur,
>>
>> I think the key issue was "getting it installed". Some systems are
>> so locked down that it isn't possible to get winzip installed on
>> machines when needed.
>>
>> Charlotte Foust
>>
>> -----Original Message-----
>> From: Arthur Fuller [mailto:artful at rogers.com]
>> Sent: Wednesday, May 26, 2004 7:27 AM
>> To: 'Access Developers discussion and problem solving'
>> Subject: RE: [AccessD] File Slice/Splice
>>
>>
>> Just out of curiosity, what is the security-paranoid distinction
>> between code you write and code that somebody known worldwide such as
>> the author of WinZip wrote? (I realize that you too are known
>> world-wide, at least among Access cognoscenti, but that wasn't my
>> point.) Frankly, from my point of view, I would sooner trust WinZip
>> than my own efforts to do the same. After all, they're on Version 9
>> or so!
>>
>> Arthur
>>
>> -----Original Message-----
>> From: accessd-bounces at databaseadvisors.com
>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jürgen Welz
>> Sent: Wednesday, May 26, 2004 10:17 AM
>> To: accessd at databaseadvisors.com
>> Subject: [AccessD] File Slice/Splice
>>
>>
>> I'm looking for some VBA to cut a file into chunks of a size that can be
>>
>> emailed and then reassemble the full size at the destination. I've been
>>
>> playing with File I/O for a few hours, opening binary, reading into a
>> string
>> or byte array and then Output to new files but it looks like I'm
>> getting a
>> few additional bytes in the reconstituted file. Presumably I'm
>> adding some
>> delimiter to the file segments that mess up the file since it appears
>> I'm
>> adding two bytes for each chunk plus another two overall.
>>
>> Does anyone have a solution? This is for sending large graphics
>> files in
>> that security paranoid place I was formerly employed. They have an
>> attachment size limit of 5 megs and a bunch of 18 - 24 megabyte tiff
>> files
>> that need to be sent out and, as usual, the IT department will not
>> budge.
>> Winzip and it's disk spanning would be ok but there's no getting it
>> installed.
>>
>>
>> Ciao
>> Jürgen Welz
>> Edmonton, Alberta
>> jwelz at hotmail.com
>
>
> _________________________________________________________________
> STOP MORE SPAM with the MSN Premium and get 2 months FREE*
> http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines
>
>
--
Marty Connelly
Victoria, B.C.
Canada