Windows 10: Excel Help If poss!

Hey guys,

Wondering if someone could shed some light. I use Win 10 Excel for reports in work. On my work laptop the formatting is fine. But if I open up the same file on my PC the formatting wigs out. Essentially it looks as though it has really large margins, that can't be adjusted. Even though the margins are set the same on both documents. No matter what I do it refuses to correct itself.

Essentially the 'A' column and the '1' row (as well as the opposing sides) are indented heavily on the page.

submitted by /u/ijonoi
[link] [comments]

:)

 

help to remote connect

not sure how to use both programs u 2 suggested, i need more helpful steps thanks

 

Excel printing

Hi Joseph,

Thank you for posting your query in Microsoft Community.

Does this issue only occur with Excel file or nay other files?

Try to copy the excel file to the other drive and check if it is working?

Run Print Troubleshooter

The built-in Printer Troubleshooter can automatically detect and fix most of the incorrect settings and errors that could cause issues while printing. I would suggest you to run this troubleshooter to check if there is any issue with the sound. Refer
top these steps:

• Click on Troubleshooting and select the
  view all option on the left pane.
  
• Click on Printer troubleshooter and follow the online instructions.

If this doesn’t help. Try to repair the Microsoft Office Application.

Do let us know if you have any other queries pertaining to Windows in the future. We will be happy to help.

Thank you.

 

Export All Administrative Events to Excel


To analyze events, from the Windows Event Viewer, there is a simple way to export all Administrative Events to Excel, with PowerShell.

Exporting all Administrative Events to Excel is a simple two Step process, as described here:

Step 1 - Create the Administrative Events View .xml file

1. Open Eventviewer (%windir%\system32\eventvwr.msc)
2. Navigate to: Event Viewer (Local) > Custom Views > Administrative Events
3. In the “Actions” pane select “Filter Current Custom View”.
4. Select the the XML tab.
5. Press Ctrl+A to select all the XML code of the Custom View.
6. Open a notepad, paste the selected code and save the file to your Desktop as AdmEvtView.xml

Step 2 - Create the csv file with the events

1. Download the ExportEvtCSV.zip file, which contains the script ExportEvtCSV.ps1 and unzip it, on your Desktop.
   It's not a fancy script, just basic PowerShell commands to create a csv file on the Desktop.
2. In Windows Search, type “ISE” (without the quotes) to open “Windows PowerShell ISE” and Run as administrator
   
3. To allow running the script, change the ExecutionPolicy, for this session. To do that, in the Console pane type:
   Code:
   
   Code:

   Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass -force

4. In the Windows PowerShell ISE, open and run the script: ExportEvtCSV.ps1
   The script will create a csv file with a name YYYYMMDD.HHMM.csv on the Desktop
5. When done, open the newly created .csv file, format the columns as needed and optionally save it as .xlsx, if you wish.

That’s it! You now have all the Administrative Events in Excel for filtering and further analysis.

Now to the more technical hard stuff... *Confused

There is a reason for running the script from within PowerShell ISE!

It would be great if everything was also working perfectly, when running the script from an elevated PowerShell too.

We can run it from an elevated PowerShell, which means that you just follow the Step 1, as above but for the Step 2 instead of the ISE you run the script from an elevated PowerShell.

The problem is that it will work only for anybody who has en-US format for the dates. Everyone else, who has another format (i.e. en-GB, fr-FR, el-GR etc.), the dates are not translated properly by Excel (although the script uses the –UseCulture switch) and remain as text in the en-US format.

I'm not sure if this a bug of the "export-csv" cmdlet, but although it runs the way it supposed to from within the ISE, from PowerShell there is a problem with the dates format.
As I haven’t found a way to overcome this obstacle, any suggestion from the PowerShell gurus of the forum (like my good friend Shawn @Brink, for instance), is welcome.