Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 26 JUL 2000 11:53:40AM John Bouley wrote:

Hello,

Has anyone experienced this before:

I have an strange issue related to a specific AREV User. If logging in as that user certain tables do not contain the correct info. Although I can not see any difference between this user and others.

All users login scripts are run based on the account. The only difference is in the environments regarding the start menu.

However, if I log into Arev under user "TELESALES" I can not correctly access certain tables! When edited, the table displays some data but it is not the correct records? A look at the dictionary and it only contains two entries!

I verified that it was pointing to the correct folder by editing the Systables file. I can not find any difference between this user and other users.

I even deleted the TELESALES user and recreated it. The same problem still exists. I created a new user call TSALES and this works like all the others.

Is TELESALES a reserved word or am I missing somthing obvious?

What else could be corrupted that would not be cleared by deleting the user?

Thanks,

John Bouley


At 26 JUL 2000 02:17PM Warren wrote:

In cases like these it is usually differences in attaches.

Check the startup/login process defined in the environment.

Check to see if there are two or more VOC files in different volumes for the same account/application which may get attached or not depending on the login process.

Check the VOC entries LOGIN, LOGON, accountname (i.e. TELESALES), username (i.e. JOHN).


At 27 JUL 2000 08:45AM Ian Lord wrote:

It may also pay to check to see if there is an "attachimage" on the

sysenv table from sysprog which contains an invalid volume pointer

for that table


At 27 JUL 2000 02:07PM Don Miller - C3 Inc. wrote:

Check SYSTEM or SYSENV for ATTACH_IMAGE records. There may be any of the following:

_IMAGE

_IMAGE

LOGON_IMAGE

If you start arev with AREV APPNAME|USERNAME IMAGE_NAME/M4096X it will attempt to use the named image.

Sometimes an image gets corrupted or you modify the file specs without resetting the image and strange things will happen.

Also, do not use SETATTACH unless all users use identical drive mapping since the image will use the drive-letter that was in effect when the image was created.

Don Miller

C3 Inc.


At 31 JUL 2000 09:57AM John Bouley wrote:

Thanks to everyone who responded.

I did not even think about the SetAttach Images. I will investigate and let you know if that was it.

Thanks again,

John Bouley

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/9091ce7992bafbf08525692800574fc3.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1