Some people recommend using ….control + alt + end on a RDP session to bring up that Windows Security screen, but it does NOT work on nested RDP sessions.

This procedure is the only one which worked for me on a Windows 2012 R2 RDP session:

1. Click Start
2. Type osk (to bring up the on screen keyboard)
3. Hit enter
4. Once the on screen keyboard is open, hold ctrl+Alt on your physical keyboard, then click on the del key in the on screen keyboard.
5. Minimize the on screen Keyboard
6. Click Change a password.

If your view is set to "datasheet view", then it is only for people with contribute rights or above for the list. If you want a user with read-only rights (Vistors) to be able to view the list, then you have to create a view using "Standard View," and set that to the default view.

QUESTION:

We are using the Bamboo Data-View Web Part in SharePoint 2013 to allow users to filter and export results from a single Library and I have just discovered that the Filter is hidden in a column when you have a Multiple Lines of Text in the grid. This makes the tool pretty useless now so I was hoping that someone has come across a better Web Part?

ANSWER:

So the answer is that Multi-line Text fields in SharePoint are NOT searchable or Filterable, end of story. I have found a solution that works. This solution is to keep a SQL Server table update to date with the library data, less the documents of course, and use a nvarchar(4000) column for the multi-line text fields. We will never exceed that number of characters so this works great plus it's much faster than rendering a SharePoint Library!

If this happens then check the Application Event Log. If you see the message below then you need to change your registr settings

MAPISendMail: Failed to submit message. Attachments to the message exceeded the size limit set by your Administrator.

Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Preferences

If there is a Key called MaxiumAttachmentSize then delete it or enter a value of 1000+. Setting it to zero appears to cause this error. 

Helpfull link: https://support.microsoft.com/en-ca/help/2813269/attachment-size-exceeds-the-allowable-limit-error-when-you-add-a-large 

https://stackoverflow.com/questions/15492004/delete-top-2-in-access

DELETE FROM (SELECT TOP 2 * FROM Table1) 

https://stackoverflow.com/questions/7892334/get-size-of-all-tables-in-database 

Is there an easy way to determine how much space on disk each table is consuming?

SELECT 
    t.NAME AS TableName,
    s.Name AS SchemaName,
    p.rows AS RowCounts,
    SUM(a.total_pages) * 8 AS TotalSpaceKB, 
    CAST(ROUND(((SUM(a.total_pages) * 8) / 1024.00), 2) AS NUMERIC(36, 2)) AS TotalSpaceMB,
    SUM(a.used_pages) * 8 AS UsedSpaceKB, 
    CAST(ROUND(((SUM(a.used_pages) * 8) / 1024.00), 2) AS NUMERIC(36, 2)) AS UsedSpaceMB, 
    (SUM(a.total_pages) - SUM(a.used_pages)) * 8 AS UnusedSpaceKB,
    CAST(ROUND(((SUM(a.total_pages) - SUM(a.used_pages)) * 8) / 1024.00, 2) AS NUMERIC(36, 2)) AS UnusedSpaceMB
FROM 
    sys.tables t
INNER JOIN      
    sys.indexes i ON t.OBJECT_ID = i.object_id
INNER JOIN 
    sys.partitions p ON i.object_id = p.OBJECT_ID AND i.index_id = p.index_id
INNER JOIN 
    sys.allocation_units a ON p.partition_id = a.container_id
LEFT OUTER JOIN 
    sys.schemas s ON t.schema_id = s.schema_id
WHERE 
    t.NAME NOT LIKE 'dt%' 
    AND t.is_ms_shipped = 0
    AND i.OBJECT_ID > 255 
GROUP BY 
    t.Name, s.Name, p.Rows
ORDER BY 
    t.Name

You created a DLL in Visual Studio 2010 so you can reference it in MS Access VBA.

It works fine in 32-bit Office but you get an error (error 429 activex component can't create object) when trying to run in 64-bit Office.

Solution: Unfortunatley non built-in ActiveX objects cannot be created in 64-bit Office and there is no direct work around for this.

I ran into a very strange error recently when I took over someone elses MS Access project. The so called developer did not use Option Explicit anywhere in the code so I added it into all modules and fixed all the misspelled variables and missing variables. Then the final Error I got when compiling was "Procedure Too Long"! That was odd as the routine in question was maybe 1000 lines long so it was NOT too long at all. After reviewing the code in more detail I decided to change some of the massive If-Then-Else blocks into Case Statements and just like magic, after the first one, I was able to get past this stupid error.

There must be some sort of limitation on the number of If-Else statements in VBA routines.

from here: https://www.lifewire.com/increase-outlook-attachment-size-limit-1173679 

Increase the Outlook Attachment Size Limit

To change the size Outlook allows as a maximum for attachments to send:

1. Press the keyboard shortcut Windows-R.
2. Type "regedit" in the Run dialog.
3. Click OK.
4. Travel down the registry tree to the entry corresponding to your Outlook version:
   • Outlook 2010: HKEY_CURRENT_USER\­Software\­Microsoft\­Office\­14.0\­Outlook\­\Preferences.
   • Outlook 2013: HKEY_CURRENT_USER\­Software\­Microsoft\­Office\­15.0\­Outlook\­\Preferences.
   • Outlook 2016: HKEY_CURRENT_USER\­Software\­Microsoft\­Office\­16.0\­Outlook\­\Preferences.
5. Double-click the MaximumAttachmentSize value.
   • If you cannot see MaximumAttachmentSize:
     1. Select Edit | New | DWORD Value from the menu.
     2. Enter "MaximumAttachmentSize" (not including the quotation marks).
     3. Press Enter.
     4. Now double-click the MaximumAttachmentSize value you just created.

1. Enter the desired attachment size limit in KB under Value Data:.
   • To set a size limit of 25MB, for example, enter "25600."
   • The default value (with MaximumAttachmentSize not present) is 20MB or 20480.
   • For no attachment file size limit, enter "0." Practically all mail servers have a size limit, though, so "0" is not recommended; you would invariably get large messages back as undeliverable after an often long and fruitless uploading process.
   • Ideally, the limit corresponds to your mail server's limit. Reduce the Outlook limit by some 500KB to allow wiggle room.

1. Click OK.

Simple, easy and cheap.

https://docs.microsoft.com/en-us/azure/backup/backup-configure-vault