Like Jim said. It's likely opening files into named/common. It may also be setting up some type of "system variables" into common as well.
You will likely need your app vendor to let you know what needs to be added. You would then have to call a subroutine of your making to call the setup the required variables which would then call the requested subroutine. You may also be able to setup a routine that calls the "regular" login/setup routine for the app and then calls the requested subroutine. Note that you would have to do this on the UniData side. I don't think there is anyway to pull back common values in UniObjects. Unless you could write a routine that did that manually.... hth -- Colin Alfke Calgary, Alberta Canada "Just because something isn't broken doesn't mean that you can't fix it" Stu Pickles >-----Original Message----- >From: peter watson [mailto:[EMAIL PROTECTED] >Sent: Thursday, May 20, 2004 1:41 PM >To: [EMAIL PROTECTED] >Subject: [U2] RE: U2] Error 30107 when calling Subroutines from >UniObjects > > >Hi all who have tried to help > >we (my company) have just had a reply from our application >vendor, they have stated that to enable UniObjects to run >there subroutines they would have to rewrite them to enable >root or a login that does not process the startup routines to run them. > >does anyone know what area I should be getting the more >knowegable people to look in for what needs starting, as >advised by Jim I would like to try an INIT >paragraph. > >Pete > [snip] ------- u2-users mailing list [EMAIL PROTECTED] http://www.u2ug.org/listinfo/u2-users
