In OI 3.5, we have deployed a runtime with access to ORMAIN (report builder) We initially had problems and Andrew McAauley suggested we had somkehow failed to deploy the SYSENV record ORMAIN_RESOURCES. This turned out to be true, and when this was done, it solved the problems….completely on one deployment (standalong) but on another on a network, we get the message "Failure to read resource record" when we Open an existing report defination. We click OK and go on and have anomolies regarding save as, save, etc. The ORMAIN_RESOURCE record is loaded, and in fact the error messages contained it that record are displayed when appropriate.

    Would like to resolve the "Failure to ......" thinking that may also solve the save as problems.  Does anyone know the source of this error message and how to eliminate the cause?

Thanks,

[email protected]

ARCS, Inc.

[/url]

Paxton,

following is the excerpt from the resource loader (function ResToString) that shows the only two cases when the loader returns the message in question (WinName is passed in – in your case "ORMAIN")

equ SYS_WINDOW$ to "SYSTEM"

equ RESOURCE_SUFFIX$ to "_RESOURCES"

equ CACHE_RESOURCES$ to "@RESOURCECACHE"

equ RESOURCES_DNE$ to "Failure to read resource record!"

…

open "SYSENV" to sysenv_fh then

  read ResCache from sysenv_fh, ResName then

• read was successful so cache the the resources so the read is

• done only once

    if WinName=SYS_WINDOW$ then

      ResCache@=ResCache

    end else

• window resources are cleared from memory when the window

• goes away

      PS_Set_Property(WinName, CACHE_RESOURCES$, ResCache)

    end

  end else

• read failed, return nothing

    return RESOURCES_DNE$

  end

end else

• open failed return nothing

  return RESOURCES_DNE$

end

…

As you can see this could only happen if the SYSENV table is unaccessible or the record doesn't exist.

Gene

View this thread on the forum...