Windows 10: Problems exporting MySQL file type as excel sheet

Why does MySQL Workbench export tables as a MicrosoftEdge HTML files despite assigning Excel Spreadsheet or XML file types? It seems as if MicrosoftEdge overrides the MySQL export file type instruction. Any clues on how I can fix this would be awesome .

:)

 

Convert EXCEL sheets to MySql / MariaDB with links to music

Hi folks
I'm trying to create a decent Music Database

Basically rather than messing around with zillions of files / tracks / playlists etc I want to use one of the Free database systems (MySQL / MariaDB - both similar and work on Windows).

I have a load of spreadsheets -- what I want basically to start testing (can add other fields later) is for Album title, file / track name and path where the link will be able to link directly to the music track and application will play the file

Using this type of database I can then create my own queries if I want specific music etc

Once you get 1 TB or more of music data using traditional libraries / playlists etc doesn't really cut it any more

For the spreadsheets I used Mp3tag to save as csv, imported into excel where the ';' character is used as mp3tags delimiter and now I want to import these spreadsheets into MySQL -- not sure though how to handle the binary objects (the music files)

Here's a typical spreadsheet I want to import into the DB.





Any ideas anyone

From the sample spreadsheet shown above -- just a small test to start with say 3 or 4 fields in the DB would be fine -- I can expand later -- what I need is the best way of handling the binary files - MariaDB or MySQL are so similar - either will do.

I don't want proprietary systems - most music type libraries - especially for consumer stuff usually break quite often and have problems if they expand over several disks or you swap disks around. MySQL / MariaDB are open source and robust so no probs there.

Any DBA's out there -- probably simple - 90 secs work for you gurus. !!


Cheers
jimbo

 

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.

 

EXCEL SHEET IN MAP XML FILE DELETE IN EXCEL SHEET

EXCEL SHEET IN MAP XML FILE SO EXCEL SHEET WORKING NO PROPERLY SO I HAVE DELETE XML MAP IN EXCEL SHEET