@key function
Craig Tooker
craig at cwtsoftware.com
Wed Feb 23 07:33:52 PST 2011
On 2/23/2011 09:47, Richard Kreiss wrote:
> Windows server 2008
> Workstation: Win XP Pro
>
> Received a call from a client's office manager this A.M> telling me the
> @keyO function was not working.
>
> I received an email from her boss saying that the function worked on his
> computer. When I tested the function through terminal server, it worked.
>
> /Ken define Not work
I think you are trying to indicate an *ML tag - at least I now know you
read his emails.
> Not work - nothing happens - the popup update fails to come up
>
> /ken define not working
>
> To continue, I called the office manager and asked her if she was having
> this problem in all of the sessions she had open. The problem was in 2 of
> the 5 sessions she had open. She is normally accessing 5 different files,
> one in each session.
I'm not a windows guy but I think it's possible to have your fP programs
located on the workstation. If that is true in your environment and the
versions are out of sync or one is dclerk and one is rclerk you could
have a token file out of sync.
> My question is, what might cause an @key function to fail to execute?
If the problem is not solved above, please post the @keyO processing so
we can try to help.
>
> Richard Kreiss
> GCC Consulting
> rkreiss at gccconsulting.net
>
>
>
>
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
More information about the Filepro-list
mailing list