Macros containing screen objects stopped working

[Erentur]

We have a problem in our enterprise on one machine running Windows NT and EXTRA! Client 6.2 SP2. All of a sudden macros containing screen objects stopped working without a reason (they worked normally until that day and continue to work on all other machines).
While executing the macros (example below) the following error message is shown (translation in brackets, as we use a german client):
Fehler von EXTRA! Basic (Error from EXTRA! Basic)
Eigenschaft oder Methode existiert nicht (Property or method doesn't exist)
Zeilennummer: 11 (Line number: 11)
Makro-Wiedergabe wird abgebrochen (Macro execution will be terminated)

Here is a snippet of one of the affected macros:

Option Compare Text

Sub Main
    '$CStrings
    
    Dim System As Object, Session As Object, Screen As Object, Ueberschrift, Fehler, Kunde1 as string, Kunde2, kunde3, kunde4, i, check
    
    
    Set System = CreateObject("EXTRA.System")      
    Set Session = System.ActiveSession
    Set Screen = Session.Screen

The affected line is the "Set Screen = Session.Screen".

As said above, the above macro (and all others) worked fine and stopped working from one day to the other without any reason. I reinstalled EXTRA! several times, also cleaning the registry from any entries concerning the software, without success, the problem persists.
I assume that somehow the macro "thinks" the client is not running and stops working as no screen seems to be available, but can't trace the source of that problem.

I hope someone here is able to help me with that problem, thanks in advance.

 

[calculus]

Try:

Set Screen = Session.ActiveSession

Currently you aren't telling Extra which Session to choose.

calculus

 

[Erentur]

Thanks for the hint, unfortunately it didn't work. Same error is thrown, macro execution is stopped.
Those macros do work on all other machines, only the mentioned one won't execute them. Any other ideas how to solve this problem ?

 

[Skie]

Are you sure you're obtaining a session? Try this.

Sub Main
    Dim System As Object, Session As Object, Screen As Object    
   
    Set System = CreateObject("EXTRA.System")      
    Set Session = System.ActiveSession
    If Session Is Nothing Then
        MsgBox "No Session"
    Else
        Set Screen = Session.Screen
    End If
End Sub

 

[Erentur]

The same error is thrown while executing this macro. Line number 9 gives the following error:

Fehler von EXTRA! Basic (Error from EXTRA! Basic)
Eigenschaft oder Methode existiert nicht (Property or method doesn't exist)
Zeilennummer: 9 (Line number: 9)
Makro-Wiedergabe wird abgebrochen (Macro execution will be terminated)

It really seems, that no session is obtained, though the EXTRA! client is surely running. Any ideas what causes this error ?

 

[Skie]

What happens if you do this?

Sub Main
    Dim System As Object, Session As Object, Screen As Object    
   
    Set System = CreateObject("EXTRA.System")      
    Set Session = System.ActiveSession
    If Session Is Nothing Then
        MsgBox "No Session"
    Else
        MsgBox Session.Name
    End If
End Sub

 

[Erentur]

Same error in line number 9, as usual. Any hint ?

 

[Skie]

It seems you're able to acquire a session. Maybe it's a corrupt/missing dll issue?

 

[Erentur]

I assume it is indeed an installation issue, the problem only is, that I reinstalled the client several times and cleaned
the registry of any entry belonging to Attachmate. The error still persists and only on that machine. Looks like there is no other chance but to reinstall the OS, or is there a way to determine what component the client is missing ?

 

[rictom]

I had the same problem.
You could try configure the system variable:
a) click with the right button in 'my computer'
b) Select the tab 'advanced'
c) click 'system variables'
d) Create a variable 'Path' with the value 'C:\Program Files\E!PC
e) reboot the computer.
I think the error 'Property or method doesn't exist' occurs because the system can´t find the Extra.

 

[Erentur]

Thanks for the hint, unfortunately it didn't solve the problem, the error message still persists.