Added an amount of documentation for MSAccess provider
Intial ODBC type provider code
Implemented linked tables, BUT it gives a nasty OleDB error in FSI. It does work in compiled projects. OK for now.
Trying to make individuals work but failing
Finally got column names working from schema file
Merge branch 'linkedtbls' of https://github.com/bennylynch/SQLProvider into bennylynch-linkedtbls

Conflicts:
	src/SQLProvider/Providers.MSAccess.fs
fixed:
 - order by clauses not working if they are the only thing in the query
 - order by clauses not working if they appear before an auto-tuple occurs that renames the table alias
major changes -
1) Individuals - thread data context through provided types to honour different connection strings at runtime
2) Connection cache now caches ISqlProvider instances via the type provider type name only - no connection strings.
3) Entities now remember their connection string (hidden from intellisense).  This is important because for further queries  from the entity, we need to understand which connection string was used when originally creating it as there may be several data contexts for the same type provider hanging around
4) Big connection lifecycle cleanup - connections are now used and then closed immediately both in design-time and runtime
5) Changed link data in the SqlQuery from a map to a list - multiple explicit joins were not working properly because the order in the query was not being preserved
6) removed static lookups in MSAccess as they were causing the design-time code to bomb sometimes (we can maybe revisit a similar optimization for all providers using concurrent dictionaries in the future)
reapply internal modifiers to some types
fix some issues introduced to access when I removed the static lookups
add missing con.open() in executeScalar
Support for Skip in MySql.

Add Skip value to LIMIT clause. Supports just Skip and no Take by
passing UInt64.MaxValue as the take limit if just Skip is given.
Merge pull request #51 from Frassle/MySqlSkip

Support for Skip in MySql.
Support for string StartsWith and EndsWith.
Merge pull request #53 from Frassle/StringWith

Support for string StartsWith and EndsWith.
GetDataContext with runtime resolution path.

This allows the runtime context to use a different resoultion path to
the development context used in the type provider.
Merge pull request #54 from Frassle/ContextCtor

GetDataContext with runtime resolution path.
Merge remote-tracking branch 'origin/master'

Conflicts:
	src/SQLProvider/SqlRuntime.Common.fs
	src/SQLProvider/SqlRuntime.QueryExpression.fs
Open connection if its closed so type ODBC type provider doesn't randomly stop working.
Fixes select, still get no results when there's a where
Architectural changes paving the way for CRUD operations.  Specifically, I have now removed all the static methods on the data context type.  Data contexts are now threaded through and erased to (or at least hidden and unboxed to) in most places via use of the new ISqlDataContext interface, and the quotations make use the of their new instance methods to do things such as retrieving related entities.
This separation will allow us to A) still keep the idea of "runtime data context" and "design time data context" separate, whilst able to share the ISqlProvider instances yet allowing connection string and resolution path differences in the runtime created versions,  and B) the entities now know about the data context they were generated from, which will be essential going forward to provide transactional update operations scoped to the correct context.

Not fully tested yet.  Also fixed a load of spelling mistakes and removed some unnecessary comments.