Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Unwanted Warning Message

Discussion in 'Information Technology' started by Wicked Wizard, Oct 28, 2005.

  1. Wicked Wizard

    Wicked Wizard
    Expand Collapse
    Guest

    We have a tool for some business contacts built in Access 2003 and
    running on XP. A colleague built it, I am involved in installing and
    training users.

    In 90% of cases, when the tool is launched 3 warning messages arise:

    1. Security Warning: unsafe expressions are not blocked. Do you want to
    block unsafe expressions? There are Yes/No/Help buttons but Help is
    dead. To proceed one chooses No.

    2. Security Warning: Unsafe expressions are not blocked. To block
    unsafe expressions Microsoft Jet 4.0 Service Pack 8 or later must be
    installed. To get the latest version of Jet 4.0 go to
    http://windowsupdate.microsoft.com

    'Path/File Name.mdb' may not be safe to open if it contains expressions
    that were intended to harm your computer. Do you want to open this
    file? There are Yes/No buttons, and one selects Yes to proceed.

    3. Security warning: Opening Path/filename.mdb
    This file may not be safe if it contains code that was intended to harm
    your computer. Do you want to open this file or cancel the operation?
    There are Cancel/Open buttons and one selects Open to proceed.

    This is a real nuisance - it would almost be better if it was
    invariable, because then we'd believe our code was at fault. I suppose
    it may be.

    Can anyone please cast any light on what is happening, what can be done to
    avoid the warning messages, and why it only happens in 90% of cases
    please? In a recent install, on 5 apparently identical networked
    workstations, installed and maintained by the same IT consultancy, 4
    produced the warnings, one did not.

    WW
     
  2. Loading...

    Similar Threads Forum Date
    India Name changes in store for girls called Unwanted Breaking News Oct 22, 2011
    India India's Unwanted Girls Breaking News May 23, 2011
    India's Unwanted Girl's Hard Talk Oct 23, 2007
    UK Summer Warnings over Forced Marriages Breaking News Aug 10, 2013
    Canada Warning: your Internet may not work on Monday Breaking News Jul 7, 2012

  3. Jeff C

    Jeff C
    Expand Collapse
    Guest

    For each instance of Access the program security settings for macros must be
    set to low.

    Tools/Macro/Security/ set to low

    Try that to see if your issue resolves

    "Wicked Wizard" wrote:

    > We have a tool for some business contacts built in Access 2003 and
    > running on XP. A colleague built it, I am involved in installing and
    > training users.
    >
    > In 90% of cases, when the tool is launched 3 warning messages arise:
    >
    > 1. Security Warning: unsafe expressions are not blocked. Do you want to
    > block unsafe expressions? There are Yes/No/Help buttons but Help is
    > dead. To proceed one chooses No.
    >
    > 2. Security Warning: Unsafe expressions are not blocked. To block
    > unsafe expressions Microsoft Jet 4.0 Service Pack 8 or later must be
    > installed. To get the latest version of Jet 4.0 go to
    > http://windowsupdate.microsoft.com
    >
    > 'Path/File Name.mdb' may not be safe to open if it contains expressions
    > that were intended to harm your computer. Do you want to open this
    > file? There are Yes/No buttons, and one selects Yes to proceed.
    >
    > 3. Security warning: Opening Path/filename.mdb
    > This file may not be safe if it contains code that was intended to harm
    > your computer. Do you want to open this file or cancel the operation?
    > There are Cancel/Open buttons and one selects Open to proceed.
    >
    > This is a real nuisance - it would almost be better if it was
    > invariable, because then we'd believe our code was at fault. I suppose
    > it may be.
    >
    > Can anyone please cast any light on what is happening, what can be done to
    > avoid the warning messages, and why it only happens in 90% of cases
    > please? In a recent install, on 5 apparently identical networked
    > workstations, installed and maintained by the same IT consultancy, 4
    > produced the warnings, one did not.
    >
    > WW
    >
    >
    >
     
  4. Jeff Conrad

    Jeff Conrad
    Expand Collapse
    Guest

    See this page on my site for links giving detailed information:

    http://home.bendbroadband.com/conradsystems/accessjunkie/macrosecurity.html

    --
    Jeff Conrad
    Access Junkie - MVP
    http://home.bendbroadband.com/conradsystems/accessjunkie.html
    http://www.access.qbuilt.com/html/articles.html

    "Wicked Wizard" wrote in message:
    news:C9n8f.5048$iZ4.442@newsfe2-gui.ntli.net...

    > We have a tool for some business contacts built in Access 2003 and
    > running on XP. A colleague built it, I am involved in installing and
    > training users.
    >
    > In 90% of cases, when the tool is launched 3 warning messages arise:
    >
    > 1. Security Warning: unsafe expressions are not blocked. Do you want to
    > block unsafe expressions? There are Yes/No/Help buttons but Help is
    > dead. To proceed one chooses No.
    >
    > 2. Security Warning: Unsafe expressions are not blocked. To block
    > unsafe expressions Microsoft Jet 4.0 Service Pack 8 or later must be
    > installed. To get the latest version of Jet 4.0 go to
    > http://windowsupdate.microsoft.com
    >
    > 'Path/File Name.mdb' may not be safe to open if it contains expressions
    > that were intended to harm your computer. Do you want to open this
    > file? There are Yes/No buttons, and one selects Yes to proceed.
    >
    > 3. Security warning: Opening Path/filename.mdb
    > This file may not be safe if it contains code that was intended to harm
    > your computer. Do you want to open this file or cancel the operation?
    > There are Cancel/Open buttons and one selects Open to proceed.
    >
    > This is a real nuisance - it would almost be better if it was
    > invariable, because then we'd believe our code was at fault. I suppose
    > it may be.
    >
    > Can anyone please cast any light on what is happening, what can be done to
    > avoid the warning messages, and why it only happens in 90% of cases
    > please? In a recent install, on 5 apparently identical networked
    > workstations, installed and maintained by the same IT consultancy, 4
    > produced the warnings, one did not.
     

Share This Page