EXTRA Error 1

[georgiy]

Hi,

When I try to print from any Extra application, the following message appears:

EXTRA.exe has generated errors and will be closed by Windows.
You will need to restart the program.
An error log is being generated.

It happens very often and seemingly does not depend on the printer or memory lack.

Could anyone help?

georgiy

 

[georgiy]

That's about Extra Version 6.5 Sorry...

 

[calculus]

Is it isolated to 1 PC or many? If 1 you may try to reinstall the app.

 

[georgiy]

Only mine is involved. Extra's been reinstalled for a couple of times

 

[chihab]

I did have this problem before on 3 workstations. I upgraded to Extra 6.7 and the problem gone.

 

[georgiy]

Eventually I removed the Attachmate Printer Button and installed mine firing a slightly modified printing macro provided with April 23, 2003 posting. It works flawlessly

 

[dcowin]

georgiy - could you send me the macro code you used to fix your problem? We're having this on several pcs and I need to find a fix for it.
Thanks for your help!

 

[georgiy]

Sorry for the delay. The code follows:

Sub Main
' Get the main system object
Dim Sessions As Object
Dim System As Object
Set System = CreateObject("EXTRA.System&quot ' Gets the system object
If (System is Nothing) Then
Msgbox "Could not create the EXTRA System object. Stopping macro playback."
STOP
End If
Set Sessions = System.Sessions

Dim rc%
Dim MaxColumn%
Dim row%
Dim MaxRows%
Dim filenum%
Dim Screenbuf$
Dim linebuf$
Dim FileName$
Dim NL$
Dim CR$
Dim FF$

' Get the necessary Session Object
Dim Sess0 As Object
Set Sess0 = System.ActiveSession
If (Sess0 is Nothing) Then
Msgbox "Could not create the Session object. Stopping macro playback."
STOP
End If
If Not Sess0.Visible Then Sess0.Visible = TRUE
Sess0.Screen.WaitHostQuiet(g_HostSettleTime)

NL$=Chr(10)
FF$=Chr(12)
CR$=Chr(13)
FileIn=FreeFile
'Takes a "snapshot" of current screen and stores it in variable Screenbuf$
MaxRows%=Sess0.Screen.Rows()
MaxColumns%=Sess0.Screen.Cols()
Screenbuf$=""
linebuf$=Space$(MaxColumns%)
For row%=1 to MaxRows%
linebuf$=Sess0.Screen.Area(row%,1,row%,MaxColumns%,xBlock)
Screenbuf$=Screenbuf$+linebuf$+Chr$(13)+Chr$(10)
Next
Screenbuf$=Screenbuf$ & NL$ & NL$ & NL$ & NL$ & _
NL$ & NL$ & NL$ & NL$ & NL$ & NL$ & NL$ & NL$ & NL$ & NL$ & NL$ & _
NL$ & NL$ & NL$ & NL$ & NL$ & NL$ & NL$ & NL$ & NL$ & NL$ & NL$ & _
NL$ & NL$ & NL$ & NL$ & NL$ & String(20, "_&quot & NL$ & NL$ & CR$ & Now()
filenum%=Freefile
'PRINT FILENUM%
FileName$="LPT1" 'name of your printer
Open FileName$ For Output as filenum%
Print # filenum%,screenbuf$; FF$ 'this actually sends the screen print to the printer
Close filenum%
End Sub

 

[dcowin]

Thank you! I found another macro code on this forum and I'm trying/testing it right now. If that doesn't work, I'll try yours! I really appreciate the help - don't want to upgrade to v6.7 unless we do it enterprise wide.

 

[georgiy]

Bear in mind that some printers need an additional 'Form Feed':
Print # filenum%,screenbuf$; FF$; FF$

 

[dcowin]

Thanks - I read that several times but had forgotten it.

 

[cpankonien]

i am having this same problem, the print job is created on a mainframe at a different location, prints to a network printer on the user's same subnet. (this seems to have started when we upgraded all desktops to win2k.) i have upgraded 5 of the machines that had the problem to 6.7, one of them just reported the (same) error. the error is seemingly random, they sometimes go for days with no errors, then all of a sudden it will happen 5 times in one day. any ideas? (unfortunately i would not be permitted to use the macro given previously)...thanks in advance...

 

[dcowin]

I really think what's happening is a corruption of an Extra! session or other similar file. Something happens to corrupt it and then it has to be recreated. Strangely enough, we saw this problem when we had Windows 3.1 workstations and one of our troubleshooters narrowed it down to one of three files. We created new, uncorrupted sessions/files of the three involved and gave the users a batch file that would copy these good copies to their workstation whenever they started receiving the errors. This would fix the problem for quite awhile. I know we're many versions of Extra! away from that version and we're now on NT 4.0 and W2K as an OS but it just acts the same and does the same thing. I haven't the time to go back through the trouble shooting we did before.