Microsoft Excel...

NateO · Vice JDK and Man of the People

Microsoft Excel...

NateO · Vice JDK and Man of the People

This is not working!

http://support.microsoft.com/default.aspx?scid=kb;en-us;112030

Argh!!

-- Edited by NateO at 20:03, 2005-07-11

BrianS · Still Number One

So is Excel Stupid?

Sorry to poke fun at a frustrating time like this but I could not resist.

What exactly are you trying to do? Possible alternatives?

-- Edited by BrianS at 20:32, 2005-07-11

NateO · Vice JDK and Man of the People

I'm simply trying open a very dodgy file (more the developers fault, not Excel's) off of a very slow network, based in Phoenix.

Normally I would terminate Excel and try again, but I had another file, still open in the same instance with a lot information that I was rollling up for 100s of files and if I kill the instance, it's all gone.

I usually back up all the time, and now I remember why... This looks like an indefinite loop of some sort...

NateO · Vice JDK and Man of the People

Thanks for listening though.

Fortunately, I've automated my roll up, so I can redo it... I just didn't really want to have to...

BrianS · Still Number One

ctrl+break?

break the code?

NateO · Vice JDK and Man of the People

It's not even code. I'm not sure what's causing it, perhaps an ActiveX somewhere or something....

It just bonked out from opening it, there's no open event procedure, that I know of (can't get into it right now)...

Well, time to bite the bullet...

NateO · Vice JDK and Man of the People

Damn it. There is a Workbook Open macro, one that I wrote. It’s trying to flip the ODBC connection to a SQL Server that was taken down after I wrote the App/Code and then populate the connection with some information from the local Lotus Notes App for the DB Admins to see (so that it didn't, falsely, appear like I, personally, was logged in 500 times).

What the hell it’s still doing in there is beyond me…

-- Edited by NateO at 21:06, 2005-07-11

NateO · Vice JDK and Man of the People

Er, it's a Lotus Notes problem, the following isn't working properly, for some reason, in the Open Event:

Private Declare Function FindWindow Lib "user32" Alias "FindWindowA" ( _
    ByVal lpClassName As String, _
    ByVal lpWindowName As String) As Long

Public Function GrabUser() As String
Dim User As String
h = FindWindow("Notes", vbNullString)
If CBool(h) Then
    On Error GoTo 1
    GrabUser = NotesID
    Else: GrabUser = Application.UserName
End If
Exit Function
1: GrabUser = Application.UserName
End Function

Private Function NotesID() As String
Dim Session As Object, MailDB As Object
Dim UserName As String, MailDBName As String
Set Session = CreateObject("Notes.NotesSession")
UserName = Session.UserName
MailDBName = Left$(UserName, 1) & Right$(UserName, _
    (Len(UserName) - InStr(1, UserName, " "))) & ".nsf"
Set MailDB = Session.GetDataBase(vbNullString, MailDBName)
If Not MailDB.IsOpen Then MailDB.OpenMail
NotesID = Mid$(UserName, 4, InStr(1, UserName, "/") - 4)
Set Session = Nothing: Set MailDB = Nothing
End Function

Worked fine in my old version of Notes, not so hot in my recent upgrade. Still using R5 though, so I'm not quite sure what the problem is... Lotus screws me again...

BrianS · Still Number One

Er sorry, I use Novell Groupwise. Does Notes expose its API for you to use early binding instead of creating objects at runtime? The infinite loop was from creating an automation object right? This may be your problem

Set Session = CreateObject("Notes.NotesSession")

can you try explicitly creating a Notes object at compile time? You will need to check your references to see if you have a notes object

Groupwise's is called a GroupwiseCommander (how queer is that). Its in the Groupwise Client Library. See if you can find some documentation on the API

NateO · Vice JDK and Man of the People

For shipping I want to use Late Binding as we have users using R5 (release 5), R6, and God knows what...

But, there is a 'Lotus Notes Automation Class' library I can poke around in and check out some of my code... It looks right, but I think you're right in that CreateObject() as such is probably the culprit...

For now, because that SQL Server is down, the solution is to delete the code.

Pretty schwaggart when your own code bites you in the ass!

-- Edited by NateO at 22:12, 2005-07-11

ddvmor · **I am the Jammie King!**

Heh. I can't even see my house from here!