Related
Of the many reports I've creating in Excel VBA, I've got one report that normally launches from a scheduler with a countdown timer that will pull external data, email, then automatically close if the user doesn't press a stop button before the query process begins. I've only inserted some code that clears all cell contents and formats on the worksheet where I once had formulas and conditional formatting. After saving the report, then launching by file association as before, now only the Excel splash screen is visible while VBA runs in the background. If I insert an "Exit Sub" anywhere in any procedure that runs, from beginning to end in the code prior to the "quit" call, the application becomes visible when the code stops. It opens normally if Excel is already open. I've found that even if I manually delete the cell contents and clear formatting and save the report on a working copy of the report, it does the same thing. At no time do I hide sheets, workbook, or application. I've only found it runs normally on my own personal PC Win7-64 and Excel 2016. None of the systems report an error in the workbook.
I've tried the following without results on our business network servers and Citrix Desktops with a variety of OS's and Excel versions:
Application visible
Foreground
Windows visible
Workbook visible
Worksheet visible
Deleting the sheet and writing data to the new sheet
Manually deleting the cell contents and formats on a working version
Re-creating the report from scratch with the same code, but it still does the same thing.
Excel 2010 and 2016
32 and 64-bit versions of Excel
Operating Systems - Windows 7, 10, Server 2016
Thanks.
When a macro is long in VBA, or the task then the display starts to flicker. I think you have the same issue. So, if this is the issue then try to set the screen update off in your VBA.
To do so, go to your macro and type this code i.e.-
Application.ScreenUpdating = False
Just confirm, if its helping.
I figured out an ugly workaround. I've created a sub to call on workbook_open(). It first makes the application invisible, opens a new workbook, closes the new workbook, then makes the application visible again.
My work machine was just upgraded to Excel 2013 add I can no longer paste results from SQL Server to Excel 2013. It just turns into a long text string that I can't break apart even with text to columns. I'm not sure if it's a setting in SQL Server or Excel, but any help would be appreciated.
You can export the data by right clicking in the top left corner of the results window and selecting Select All, then selecting Copy With Headers, then pasting into Excel.
You can also Select All, then Save Results As and save it as a CSV file, then convert it to an Excel file.
The second option works best for me when the data set becomes more than a few hundred thousand rows/records.
I had created a activex multiselect listbox in one excel workbook in my machine. It was not working. On deleting MSForms.exd, it started working again. However, another excel workbook with the same piece of code for activex multiselect listbox is not working in my machine.
Same solution; restart your computer and before opening any office apps search out MSforms.exd again and delete all instances. this is apparently not a "once and for all" solution, I guess we're still waiting Microsoft's solution to their update 'faux pas.'
I have an Excel file with 4 sheets. Each sheet is pulling data from a different SQL stored procedure. I have created a button that refreshes the connection for each sheet. It works perfectly on everyone's PC . . . except for one. When you click the button on this particular person's PC, it only refreshes 3 out of 4 sheets. No error message shows up. We each have our on local copy of this Excel file. I even gave her a copy of mine and it only refreshes 3 out of 4. I am using Excel 2010.
I have a Excel Workbook in which I have created an analysis using Datatables. For some reason each time I open the workbook, the formulas that reference the Datatable turn into #Name erorrs.
The first time I opened it, I thought I had simply made a typo and needed to reenter the formula. I did that and saved the file. On opening it two minutes later.... same error!
The error is only for two referenced columns in the datatable. Other columns from the same table reference fine, without error!
Here a sample of what the error looks like:
=SUMIFS(tblDB #REF!,tblDB[AWGW 2012],$B$3,tblDB[NWGW 2012],$B13)
The file (saved as an .xlsm) contains the following, none of which are used or touched by the formulas with the error:
Pivot Tables
VBA Code (none are event based... regular subs that need to be manually started only)
Other Datatables
I have tested on the the following Systems:
Excel 2010 (32bit) and Windows XP
Excel 2010 (64bit) and Windows 7
Does anyone have any idea why this happens?