Results 1 to 14 of 14
  1. #1
    New Lounger
    Join Date
    Jan 2002
    Location
    IL, USA
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Custom Forms (OL2002)

    Does anyone know of any type of work around for the OL2002 security 'features' that prevent you from running any custom forms with VBA in them? We have a ton of custom forms that we use here, and I cannot use any of them in Office XP - even those that have been published to the Organizational Forms Library.

    Microsoft's response, when contacted, was that this is a security 'feature' to protect us <img src=/S/puke.gif border=0 alt=puke width=60 height=15>. When I followed up, they responded that I should suggest this 'new and improved' feature on their site; and possibly, maybe, MS might include it in the next release of Outlook. Gimme a break!

    Any help anybody can give to this I would HUGELY appreciate! <img src=/S/thumbup.gif border=0 alt=thumbup width=15 height=15>

    Thanks!

  2. #2
    Platinum Lounger
    Join Date
    Jan 2001
    Location
    Roanoke area, Virginia, USA
    Posts
    3,729
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Custom Forms (OL2002)

    ask the admin to install the admin form to give you permissions back.

    For more information on the security features, see <A target="_blank" HREF=http://www.slipstick.com/outlook/esecup.htm>http://www.slipstick.com/outlook/esecup.htm</A>

  3. #3
    New Lounger
    Join Date
    Jan 2002
    Location
    IL, USA
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Custom Forms (OL2002)

    Well.... almost. That does help quite a bit, and is a very nice tool for administering security settings in our organization (I'm testing it on my PC right now ... maybe will use it all over). I am the admin, so have been able to make these changes and so on myself.

    However, although this does make it so that I can run some self-contained forms that I couldn't before, I am still having problems with custom forms that access a database file. Specifically, we have a tech request form that is a modification of a template custom form from MS site that has been working great for a long time (and still works great in OL98 and OL2000). It accesses an Access database on the server for information that it populates into various fields; for some reason that Access access just does not work.

    Any ideas? I tried changing the script itself, but with no luck ...

    Thanks again for the help ...

  4. #4
    Platinum Lounger
    Join Date
    Jan 2001
    Location
    Roanoke area, Virginia, USA
    Posts
    3,729
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Custom Forms (OL2002)

    do you have all the bits installed that you need for access connectivity? the upgrade may have changed something.

  5. #5
    New Lounger
    Join Date
    Jan 2002
    Location
    IL, USA
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Custom Forms (OL2002)

    I should have ... I always do completefull install with the 2000 or XP professional. I will verify, but would be extremely surprised if that were the case (I use Access for lots of other stuff we do around here too, with no problems). Good thought though.

    MK

  6. #6
    5 Star Lounger
    Join Date
    May 2001
    Location
    Washington, USA
    Posts
    750
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Custom Forms (OL2002)

    On the Access problem you might want to check the references. Maybe you lost CDO, ADO or whatever you were using for connectivity. See Tools | Macros | Visual Basic Editor. Once there see Tools | References.

  7. #7
    New Lounger
    Join Date
    Jan 2002
    Location
    IL, USA
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Custom Forms (OL2002)

    It doesn't look like it ... I have just about every add-in known to man it appears. Remember too that these forms work just fine on any machine not running Office XP.

    If this is something machine specific, what specifically should I be looking for there? The command that actually pulls the database is:

    set rstBuilding = Item.Application.CreateObject(DAO.DBEngine3.5).Wor kspaces(0).OpenDatabase(server space and file.mdb).OpenRecordset("tblTechRepRequestBuilding ")

    Thanks to all ... keep the suggestions coming! <img src=/S/clapping.gif border=0 alt=clapping width=19 height=23>

  8. #8
    5 Star Lounger
    Join Date
    May 2001
    Location
    Washington, USA
    Posts
    750
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Custom Forms (OL2002)

    So on these XP machines, is Microsoft DAO 3.51 Object Library checked off in the references? If it's not checked it's not loaded.

  9. #9
    New Lounger
    Join Date
    Jan 2002
    Location
    IL, USA
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Custom Forms (OL2002)

    Actually that only indicates what references you want to load and use or distribute specifically with your VB or VBA project, but in any case I checkboxed 'em anyways and as expected made no difference ... the form itself works on OL98, OL2000, etc., so I would not expect that the code itself is at fault here.

    Anything else?

    BTW - these are not XP machines, they are 2000 professional and 98 machines, but with Office XP installed on them.

  10. #10
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: Custom Forms (OL2002)

    If a referenced library doesn't exist on the target machine, I think you get an error similar to "Cannot open macro storage." What error are you getting and where does it fail?

  11. #11
    New Lounger
    Join Date
    Jan 2002
    Location
    IL, USA
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Custom Forms (OL2002)

    Actually at this point, I am not getting any errors at all ... installing the overrides for the outlook security 'features' removed the warnings and such ... it just won't pull the database information.

    There seem to be 2 places where a failure could possibly occur - one would be the access of a 'task' type note in a folder that indicates where the database lies (the body of that note is the database location). I attempted to go around that by just assigning the location as a string value to the variable that would normally be filled - also other forms such as the outlook security form that requires pulling data from public forms seem to work, so I doubt this is the issue.

    The other place I can figure a problem would be with the database access itself - for some reason OL2002 won't allow a connection to be made with the database file itself, or won't allow the vba script to create a temp table, or won't allow the data pulled from the db to populate a field ... I guess I could get around this by pushing the data directly on the field, thus bypassing the whole database access, but I would prefer not to take that step.

    Thanks again for any assistance ...
    MK

    BTW, just as an aside, this is a 2000 professional machine with a new install of office xp, all service packs and etc. installed, plus attopts and the outlook security form.

  12. #12
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: Custom Forms (OL2002)

    When you say it won't pull the information, are you getting an empty recordset back? If you are using ADO, check out some of Charlotte's messages on the VB/VBA board on how to read the errors reported within the ADO object. These are more specific than the errors that percolate through to VB (which in this case don't exist anyway). There might be something helpful there.

  13. #13
    New Lounger
    Join Date
    Jan 2002
    Location
    IL, USA
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Custom Forms (OL2002)

    I wasn't able to find anything posted by Charlotte that indicated how to get to the errors reported within an ADO object (she has tons of posts - and even searching specfically 'ado error charlotte' didn't dredge up anything useful <img src=/S/dizzy.gif border=0 alt=dizzy width=15 height=15>), but I did try some other stuff ...

    When I populate a msgbox command with the variables that I should be pulling; initially the database location, then the database information from tables, those all return blank values.

    Even when I specify internal to the code the db location, still no values get populated into the data fields that should be grabbed from the dB.

    Now remember, this form and all code works perfectly on all other OSOffice installs in my organization. The ONLY configuration it will not work on is a 2000 Prof with OfficeXP. So, I really hesitate to blame the code in this case ... there's gotta be something in OL2002 or OfficeXP in general that is blocking the connectivity to this database file.

  14. #14
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: Custom Forms (OL2002)

    Can we rule out Windows 2000 itself as the problem, or does it work in Office XP on other flavors of Windows? I suspect it's something different about XP, perhaps a component that came with Office 2000 but isn't shipped with XP. But such speculation doesn't really help, does it?

    I'm sure Charlotte has some nice code to dump the error messages to the Debug window, but in the interests of brevity, try this immediately after your query (change objConn to the name of your Connection object):

    If objConn.Errors.Count > 0 Then
    Stop
    objConn.Errors.Clear
    End If

    If your routine stops, use the Locals window to review the messages from ADO. If the "error" number is zero, it is just a warning and probably doesn't explain the problem. See anything interesting?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •