System.Session Object "Cannot Update. Datebase or object is read-only"

[krisbest86]

I want to get data from the other programme. When I run the code below I get error:
3027 Cannot Update. Datebase or object is ready-only. It occurs at the line I highlighted.
Any help would be very appreciated.

Sub MainObject()

Set System = CreateObject("EXTRA.System") ' Gets the system object
System.TimeoutValue = 500
If (System Is Nothing) Then
'
Else
Set Sessions = System.Sessions
If Not (Sessions Is Nothing) Then
' Set the default wait timeout value
g_HostSettleTime = 500 ' milliseconds
OldSystemTimeout& = System.TimeoutValue
If (g_HostSettleTime > OldSystemTimeout) Then
System.TimeoutValue = g_HostSettleTime
End If
' Get the necessary Session Object

Set Sess0 = System.ActiveSession
If (Sess0 Is Nothing) Then
MsgBox "Could not create the Session object. Stopping macro playback."

Else
If Not Sess0.Visible Then Sess0.Visible = True
[highlight #FCE94F] Sess0.Screen.WaitHostQuiet (g_HostSettleTime)[/highlight]
End If
End If
End If


End Sub

 

[strongm]

Not sure I can understand how an EXTRA! Attachmate session would raise an MS Access error ...

 

[krisbest86]

why does it MS Access error and it does not when i run code in Excel file?

 

[strongm]

OK, a generic database error. But still don't see from what you've shown us here why an Extra! Attachmate session should raise a database runtime error.

 

[SkipVought]

Hi,

You have 5 IFs and only 4 End Ifs.

Check your code.

Skip,
[sub]
Just traded in my OLD subtlety...
for a NUance![/sub]

 

[strongm]

That's because one of the Ifs is not a block If, Skip.

 

[SkipVought]

Check Extra VB HELP on the syntax for waitQuietHost

Normally, the only cases when WAITING is necessary, is when you send a command to the mainframe, which processes the command asynchronously. Then you cannot simply wait a fixed period of time, like 500 ms. It's more like waiting at a stop sign in your car, until the intersection is clear of crossing traffic: you must use something like WaitForCursor in a loop until the cursor returns to the Screen Rest Coordinates.

Skip,
[sub]
Just traded in my OLD subtlety...
for a NUance![/sub]