[AccessD] This on Sharepoint

jwcolby jwcolby at colbyconsulting.com
Wed Jun 6 09:02:44 CDT 2007


I have no clue how Jet stores things in an MDB and AFAIK it is not really
published anywhere.  All I know is that storage in an Access database
appears to be fairly efficient.

I think that the point here is the right tool for the job.  Sharepoint might
just be the appropriate tool for specific jobs.  Storing relational data
does not appear at first glance to be one of them.

John W. Colby
Colby Consulting
www.ColbyConsulting.com 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: Wednesday, June 06, 2007 9:44 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] This on Sharepoint


  LOL thinking about this a bit more, I wonder if he's every looked at the
system tables in JET<g>.  JET uses basically the same techniques to store
multiple object types in a single MDB file. 

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: Wednesday, June 06, 2007 9:37 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] This on Sharepoint

John,

  It's true.  SharePoint stores everything like that.  I think the comments
you quoted are a lot of FUD.  SharePoint uses SQL Server as a data store.
If you don't trust that to get it right, we might as all quit right now.

Jim.




More information about the AccessD mailing list