Windows 10: Excel acting funny

Starting today, when clicking on an Excel cell, it automatically opens the formula on the screen, rather than what previously required highlighting the cell and going up to the Formula Bar. Very annoying.


Also, starting today, while highlighting and 'cutting' multiple cells in Excel in anticipation of 'pasting' them elsewhere in Excel, the highlighted cells lose their highlight. What is going on?

:)

 

ACT Pro 2013 will not open in Windows 10

Hi,

Thank you for posting in Microsoft Community.

The most likely causes on a standalone are a damaged or invalid .pad file or SQL is not running, or is damaged.

I suggest you to follow the steps below and check if the issue persists.

• • 
    Click your Windows Start button, choose Run and type in actdiag.
    

• • 
    When ACT! Diagnostics comes up, click Databases, the Database List.
    

• • 
    Locate your database in the list, right-click on it and select Detach. Make sure you know the filepath to your database before detaching it.
    

• • 
    When the database has been detached, open My Computer (or Windows Explorer) and browse to the location of your database.
    

• • 
    Locate the .PAD file for your database [database name].pad and delete it.
    

• • 
    Reopen ACT!...you will get a message that the last database opened cannot found, then will be taken to the Open Database dialog box.
    

• • 
    At the bottom of this box, change the Files of Type to .adf, browse to the location of your database and double-click on the .adf file for your database.
    

• • 
    You will get a message that ACT! will verify your database, click OK and ACT will reattach your database to SQL and create a new .pad file.
    
  • 
    Hope this helps.
    

 

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:
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.

 

Intel Core i7 920 Build for a friend.

Excellent fellas I will look into the smaller HAF.

I noticed several suggesting the Samsung F1 1TB. Is it really a better drive than the WD I suggested I like WD it has +2 yrs warranty over the Samsung F1 and it is only $10.00 more.

Funny you suggest the Foxconn BloodRage GTI I like it very much from reading as well. My pick was between it and the one I listed.