Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Recent content by rev0102
-
Open file, auto_open, close 1st - Breaks VB.
Right, but the remainder of the code in file2 depends on file1 being closed (file2 moves file1, then saves itself to file1's old location and name). The crummy hack I just came up with does this: Right before this command: Workbooks("1.xls").Close savechanges:=False I've added...- rev0102
- Post #5
- Forum: VBA Visual Basic for Applications (Microsoft)
-
Open file, auto_open, close 1st - Breaks VB.
By all means, Brainstorm! It's a good idea. I've tried both workbook_activate and having it just in a standard module in file2 and having file1 either activate file2 or run file2's macro in the module, but both have the same effect: file2's macro runs first before file1's can finish, file2...- rev0102
- Post #3
- Forum: VBA Visual Basic for Applications (Microsoft)
-
Open file, auto_open, close 1st - Breaks VB.
OK, so as it stands I have 2 files; 1.xls and 2.xls. file1 has a macro: Sub One() Workbooks.Open Filename:="c:/2.xls" MsgBox "You'll never see this message " End Sub and file2 has this in its ThisWorkbook: Private Sub Workbook_Open() Workbooks("1.xls").Close...- rev0102
- Thread
- Replies: 4
- Forum: VBA Visual Basic for Applications (Microsoft)
