Microsoft Access Version Comparison Matrix
Microsoft Access debuted in 1992 and recently celebrated its 25th Anniversary! Over the decades, Microsoft Access evolved with a large number of enhancements, database formats, and discontinued features. It's hard to remember all the changes. We created a page that shows the different Microsoft Access versions and changes in an easy to understand comparison matrix. Microsoft Access Version Features and Differences Comparison Matrix See when versions were released, their latest service packs, database formats, linked tables, field types, security features, Windows Operating Systems, and many other features both new and old. Hope this helps. Let us know if we missed anything.How to Properly Delete Custom Columns in SharePoint
SharePoint custom columns have been around for quite some time, but I’m finding that there’s still some confusion on how the various types are used, and more importantly how can you delete them. In this post, I’m hoping to shed some light on the topic. Custom columns form a part of your overall SharePoint Information Architecture. When properly set up, custom columns (or fields as sometimes referred to in SharePoint) are ideal for capturing metadata in a consistent way across various types of content. In SharePoint, you can create custom columns in one of two ways: Custom List Column Custom List columns are created directly within a list (or library). They can be accessed via the list and used to store information. Although quick to set up, one of the major drawbacks is that list columns are limited in scope to only the list in which you created them. You cannot leverage the site columns outside of the list. This reason alone can prevent such columns from being considered for scalable solutions where you would have to add the same columns to multiple lists or libraries throughout a SharePoint site. Custom Site Columns Custom Site columns, as their name suggests, are created at the site level. Unlike their List Column relatives, the Site columns are accessible throughout the entire site collection, where you can add them to any number of lists, libraries, and content types. When you change the Site column properties, you have the choice to propagate these changes to all instances where the Site column is in use. Deleting Custom Columns If you wish to remove a custom column, it’s important to understand your options and the ramification they have on your data as described below. Deleting a List Column As I’ve mentioned earlier, when you create a new column within a list or library (not selected from pre-existing site columns), the list owns the column, and the column is only accessible to the list. Therefore, you can easily delete it from the List Settings by selecting the column and then clicking the Delete button on the form. Keep in mind that once you delete the list column, you also lose any data associated with the column. Deleting a Site Column from a List A reference to the site column is added when you add a site column directly to a list. As mentioned above, whenever you change the site column, any instances that use it will change as well. In the example below, I’m showing a Date field that has been added directly to two lists. If you try and delete the Date site column, you will see a warning message similar to This site column will be removed and all list columns which were created from it will be permanently orphaned. Are you sure you want to delete this site column? What does orphaned mean? Well, think of the site column as being the parent that controls its children (the referencing site columns within the lists). They will behave as their parent does. When you delete the parent, then you are in essence converting the site columns within the lists into list columns that lose the relationship between them. In other words, each list will have its unique copy of the site column with all the same settings just before you deleted the site column. You cannot undo this change. Deleting a Site Column from a Content Type When you add a site column to a content type, you’re following better practices for your Information Architecture by encapsulating all required metadata into a reusable entity (content type) rather than dealing with the individual site columns in each list. On the flip side, deleting your site column now becomes a bit trickier. If you tried to remove a site column that is associated with a content type, you might have seen a message as Site columns which are included in content types cannot be deleted. Remove all references to this site column prior to deleting it. What you need to do in this case is remove the site column from each content type before removing it. But what do you do if you don’t know where it’s used? In this case, you can leverage PowerShell to help you get the answer you need. To find out what content types are using your site column, you first need to know the InternalName of your site column. You find it by going to the site column (Site Settings à Site Columns) and looking at the URL as depicted below. In my case, the field is called Date1. Now you can run the script below that is based on OfficeDev PnP to search all the content types in a site collection. The script lists all the content types that use the site column you wish to delete (NOTE: to run the code I’ve supplied below, you must install the OFficeDev PnP solution first from https://github.com/OfficeDev/PnP-PowerShell). Connect-Sponline -url "your_tenant_url" $fieldInternalName = "your_field" $web = Get-SPOWeb Write-Host "Searching for:" Write-Host "InternalName: $fieldInternalName" Write-Host Write-Host "Get Content Types" $cTypes = Get-SPOContentType | where {($_.Hidden -eq $False) -and ($_.Group -ne "_Hidden")} # Search through all the non-hidden content type and find which ones include the site column foreach($ct in $cTypes) { $fields = $ct.Fields $web.Context.Load($fields) $web.Context.ExecuteQuery() $field = ($fields | where {$_.InternalName -eq $fieldInternalName}) if ($field -ne $null) { Write-Host "Content Types: $($ct.Name)" Write-Host "Content Type ID: $($ct.ID)" } } The output will look something similar to the image below. Searching for: InternalName: Date1 Get Content Types Content Types: TestCT Content Type ID: 0x01010038A3F80D4105C845BDD6A523CB1CC969 Now you need to go to the Content Types (Site Settings à Site Content Types) and look for the content types by name. If you see any duplicates, compare the content type ID against the one listed in the URL. Just remember, removing the columns from the content type will delete the content of those columns. That’s it. Now you know what to look for when removing your custom columns. Good luck.Released: December 2016 Quarterly Exchange Updates
Today, The Exchange Team announced the latest set of Cumulative Updates for Exchange Server 2016 and Exchange Server 2013. These releases include fixes to customer reported issues and updated functionality. Exchange Server 2016 Cumulative Update 4 and Exchange Server 2013 Cumulative Update 15 are available on the Microsoft Download Center. Update Rollup 22 for Exchange Server 2007 Service Pack 3 and Update Rollup 16 for Exchange Server 2010 Service Pack 3 are also available. The updates include: - A new Outlook on the web compose experience - Support for .Net 4.6.2 - Change to Pre-Requisites installed by Setup - Update on Windows Server 2016 support - Latest time zone updates - Important Public Folder fix included in these releases Read more on The Exchange Team blog.Exchange Server 2010 End of Support is (Still) Coming!
In April 2018 we blogged about the coming End of Support date for Exchange Server 2010. It’s time for another reminder, but today’s post is extra special. Why? One year from today Exchange Server 2010 will no longer be supported. What does ‘end of support’ mean? Exchange Server, like almost all Microsoft products, has a support lifecycle during which we provide new features, bug fixes, security fixes, and so on. This lifecycle typically lasts for 10 years from the date of the product's initial release, and the end of this lifecycle is known as the product's end of support. Learn more about what this means and what your options are on the Exchange blog.Analyzing Exchange Transaction Log Generation Statistics – Revisited
Almost 4 years ago, The Exchange Team wrote a script called GetTransactionLogStats.ps1, and originally blogged about it here. At the original time of writing, the primary purpose of the script was to collect transaction log generation data, and use that to determine the percentage of transaction logs generated per hour in an environment. This could in turn be used to populate the related fields in the Exchange Server Role Requirements Calculator. Since originally writing this script, there have been significant updates to how the script functions, and also added a handful of new features along the way, which were significant enough that the team wanted to have a new post about it. Of note, the script now: Uses PowerShell Remoting to collect data from many remote servers in Parallel. This significantly speeds up collection speeds. Generates a database heat map, that compares the number of logs generated for each database to the number of logs generated for all databases. This can be used to identify databases that may be overloaded or underloaded. Uses only log generation information from active database copies to determine log generation statistics. Accepts the target servers via a script parameter instead of via a text file. Get more details on the Exchange Team blog.Migration to Modern Public Folders – Notes from the Field
This blog post goes through the documented TechNet process for migrating legacy public folders to Exchange 2013/2016, expanded with real world guidance gained from field support. Part 0: Verify public folder replication Part 1: Download the migration scripts Part 2: Prepare the Exchange 2010 server and public folders for the migration Part 3: Generate the CSV files Part 4: Create the public folder mailboxes in Exchange 2016 Part 5: Start the public folder migration Part 6: Complete the public folder migration (downtime required) Part 7: Finalize the public folder migration (downtime required) Part 8: Test and unlock the public folders Get full details and notes on the Exchange Team Blog.Confluence to SharePoint migration
https://caseagile.com/products/enterprise-bridge/confluence-to-sharepoint-migration/® is an essential part of the efficient SharePoint®deployment strategy for organizations of any structure and size. https://caseagile.com/products/enterprise-bridge/confluence-to-sharepoint-migration/® dramatically reduces the effort and time for migration to SharePoint®, eliminates migration errors and ensures that the entire corporate digital archive is seamlessly moved to new digital platform. https://caseagile.com/products/enterprise-bridge/confluence-to-sharepoint-migration/ supports Confluence on premise servers and Confluence online, SharePoint 2010, 2013, 2016 and SharePoint Online. It transfers text, images, tables, wiki pages, documents, files, videos etc. Despite evident advantages and improvements offered by SharePoint®, the decision for the actual deployment of the portal does not always come easy. It is complicated with concerns about large amounts of corporate documents spread across legacy storage sites, such as existing intranet sites, network accessible storage (NAS) and even local hard disks of user workstations. Associated expenses for content migration and potential disruptions of access during the transition can be significant arguments impeding the important management decision. https://caseagile.com/products/enterprise-bridge/confluence-to-sharepoint-migration/® resolves these concerns in a simple and elegant way by offering automated content migration scenarios enforced with elaborate transformation engine supporting conversion of data, meta-data, security and permissions. Migration of data from Confluence ® (cloud or on-premise) to SharePoint ® Online, 2016, 2013 or 2010. Migration of text, images, tables, wiki pages, documents, files, videos and other content to SharePoint ® . Spaces, when migrated to SharePoint ® are distinguished and identifiable. Pages and sub-pages, after migration, are in the same order as that of Confluence ® . Migration of most widely spread and popular Confluence ® macros. Maintains the source page formatting. Wiki pages migrated to SharePoint ® are in the same format as that of the Confluence ® in terms of text, images, links and more. Links to other Confluence ® pages and documents (Related Articles) remain intact when migrated to SharePoint ® . Created and modified dates of the spaces, pages and files remain the same after migration. Owners and contributors of the spaces, pages and files remain the same after migration, as well as permissions of users and groups as they existed on source server. Labels on each page come across when migrated to SharePoint ® . Destination SharePoint ® fields for this content are configurable through visual mapping. Support two-factor authentication and proxy. Full compliance to most rigid and contemporary corporate security standards.
"Business Intelligence Center" site template is missing when creating a new online sub-site
I am working on migrating an on-premises sharepoint 2010 site collection to sharepoint online. now the on-premises 2010 site collection contain a sub-site of type "Business Intelligent" , so i was checking if i can create such as site template inside sharepoint online. now i find this link which mentioned that this should be possible @ Create A Business Intelligence Center Site Collection In Office 365 (SharePoint Online Site) . but in our case when i tried to create a new sub-site inside our online root site collection (which is of type classic team site), i did not find any site template for BI, here is the list we got:- so i am not sure how we can create a new sharepoint online sub-site that should replace the on-premises sub-site which is of type BI?Talking SharePoint Virtual Summit with Dan Holme [VIdeo Interview]
Recapping SharePoint Virtual Summit with Dan, the Man, Holme Hi y'all! On the https://www.avepoint.com/blog/strategy-blog/dux-quax-microsoft-dan-holme/, I took a ride with Microsoft’s Director of Product Marketing for SharePoint Dan Holme to recap the 2017 SharePoint Virtual Summit! Get a front row seat as we discuss announcements made at the summit, like the new SharePoint Admin Center and hear what Dan has to say about data security in Office 365, and Microsoft’s plan of attack moving forward! Check out the video here: http://www.avepoint.com/blog/strategy-blog/dux-quax-microsoft-dan-holme/ As always, remember to keep the conversation going! Tweet your questions to Dan (@danholme) and me (@meetdux).
