Below is a Video Illustration in Excel 2010. It applies to Excel 2007 and above
Monthly Archives: March 2014
This morning I had a very interesting query from a user. The request was if he could auto-download all the attachments that he received on his Outlook to another folder other than the temporary one (default folder). I sat down for a while looking for rules or any option on Outlook itself. But nothing to be found. When I did a bit of my own research, I figured out that with a bit of coding and then using the Outlook Rules itself, this was possible.
The link found to be very helpful for this purpose. Please note that in the section where one can specify the file type that needs to be stored to the custom folder, one needs to add a double quote before the file type.
For example, here is the code that I had used for my trial runs
Public Sub saveAttachtoDisk(itm As Outlook.MailItem)
Dim objAtt As Outlook.Attachment
Dim saveFolder As String
saveFolder = “D:\Attachments”
For Each objAtt In itm.Attachments
If InStr(objAtt.DisplayName, “.pdf”) Then
objAtt.SaveAsFile saveFolder & “\” & objAtt.DisplayName
In the scenario above, the user only wanted PDF files to be saved to a folder in his D drive. The part of the code where I have highlighted as red should have the file extension (file type) within double quotes. In the link provided above this has been given within single quotes.
Although it is mentioned that this works for Outlook 2007 and Outlook 2010, I had tried on Outlook 2013 and it works beautifully without any hiccups. Give it a try! It’s awesome to see it working!
I went through the Sonicwall Forums and did not find the correct answer to this problem
I tried updating Adobe Air and Restarting the System. But still had no luck
- Open Task Manager
- Under Services Tab; locate a service named SonicWALLCDPProxy
- This service is most likely stopped. Start this service and open the Agent once again
If you are getting this error from your Server Event Logs; it is certain that your backup is not secure and urgent action needs to be taken
The high-probability for this error is that you are running on Older CDP Agent Version (possibly 6.0). With CDP Agent Version 6.0 there is an issue of agent resources leaking due to which the agent service has these panic attacks and restarts the service. In order to fix this issue it is advised to update your CDP Agent to latest available version; which as of currently is 188.8.131.52
I faced this error recently with a Blackberry Phone running OS 7.
The first thing on my mind was to check the Mobile Network Selections under Network and Connections. Strangely both Network and Connections as well as Wi-Fi Network options would not respond.
The only option left was to do backup and restoration which takes just about 30 minutes. I would suggest you do not crack your brains further on this one doing R&D.
SQL Database ‘SharePoint_Config’ on SQL Server instance ‘GDFS’ not found. Additional error information from SQL Server is included below.
Cannot open database “SharePoint_Config” requested by the login. The login failed. Login failed for user ‘GOLTENSDXB\SP_Farm’.
Before you go about making any drastic changes to the database; it would be wise to check the Status of the Sharepoint_Config database within the SQL Server Management Studio
Is your Sharepoint_Config Database set to Single User Login?
If yes, we require the trace and kill the session that is connected to this database before we enable multi user
Step 1 – Trace the Session ID connected to the Sharepoint_Config Database
select * from master.sys.sysprocesses msp,master.sys.sysdatabases msd where msp.spid>50 and msd.name='SharePoint_Config' and msp.dbid=msd.dbid
Step 2 – Kill the Session and set the Sharepoint_Config Database database to offline mode
kill <spid> [eg: kill 62] alter database Sharepoint_Config set offline with rollback immediate;
Step 3 – Switch back the Database to Online Mode and set it for Multi-User login
alter database Sharepoint_Config set online,multi_user with rollback immediate;
If your Sharepoint_Config database was not in Single User Login Mode and are still faced with this error; I would recommend below post
Is your Sharepoint_Config_Log file reaching enormous GB size of data and nearing your full drive space utilization?
Shrinking a Log File in your SQL Database may seem very straightforward when accessing SQL Server Management Studio
You may have already tried the below and still not seen any change in the file size
If the above scenario is true, it is most likely that you have set your DB in Full Recovery Mode and hence will not allow you to shrink the log file
Please note that in my illustration I have made an assumption that the default dbname Sharepoint_Config has been changed; if changed please make revisions to the script accordingly
To confirm this further, run the shrink operating using the SQL Query.
From the SQL Server Management Studio
- Click New Query and type below command
DBCC SHRINKFILE (Sharepoint_Config_LOG);
- Execute the command
- Click the Messages tab at the bottom and take note of the error
Your are most likely to get the below error
“Cannot shrink log file 2 because the logical log file located at the end of the file is in use”
In SQL Server Management Studio; run below commands use master; alter database Sharepoint_Config set recovery simple;
DBCC SHRINKFILE (Sharepoint_Config_LOG);
This will shrink the log file to its default size.
If you are faced with this problem; ask yourself two questions
- Have you used more than 1 Apple ID with the same Apple Device during its lifetime?
- Have you synchronized your iPhone with PC’s running different Apple ID’s?
If either of them are true the real reason for the error is because the version of the App that you wish to update was installed / updated / synchronized using an alternate or old Apple ID
To resolve this issue; just delete the App. When re-installing the App again from iTunes, it will automatically download and install using the current configured Apple ID on your device
Very recently, I happened to go through a very tricky situation with the printers in our office, all connected through SafeQ ports (not IP ports). The users would print, but when they went to the printers to release the jobs, the jobs were not displayed on the YSoft Terminal. I checked the print server queue and couldn’t find any pending jobs stuck in the queue. I tried restarting both the Print spooler services, that didn’t help. I tried restarting both the CML (Primary Server) and the Secondary Node (Secondary Server) and this helped for about 5 minutes. After 5 minutes or so the prints would stop appearing on the YSoft SafeQ terminal.
After having checked for more than 2 hours, I realized that the secondary partition on the Secondary server had run out of space. When checked, I was shocked to find that the ldf file for the SafeQ Database has consumed almost 90% of space on the secondary partition. Once this file was truncated, the jobs had started appearing on the terminals and the print jobs were all smooth, fast and back to normal.
After installing Movie Maker, you face the below error as illustrated
You may go through the link that shows up in the error and check the minimum system requirements. The only pointer that may catch your attention is the DirectX Version on your PC. The minimum DirectX Version expected is version 9.
To crosscheck this click Start – Type Dxdiag and press enter. The DirectX Version will be listed in the DirectX Diagnostic Tool Window that opens up. If your PC is relatively new and frequently updated; there is no reason why your DirectX Version should be below 10; so forget the minimum requirement of DirectX 9 for Movie Maker 2012
The most obvious solution to get your Movie Maker software working is to update your Display Driver
- Locate your Display Driver Model and Driver Version
- Start – Control Panel – Device Manager
- As per the illustration, the display card is Intel and hence I will proceed to the Intel Website to download and Install the latest driver (https://downloadcenter.intel.com/Default.aspx?lang=eng)
- But if in your case; it’s an NVIDIA proceed to this link instead (http://www.nvidia.com/Download/index.aspx)
- Locate your driver using the search options available on the respective Driver Manufacturer webpage.
- Download and Install the latest updates
- Once done, restart the PC and try running Movie Maker