[AccessD] Fw: Office 365 Re: You Guys make Me Sick

The difference between using SQL Server and SharePoint layered on top of SQL
Server or 365 layered on top of SharePoint layered on top on SQL Server.

You're doing it the "old school" way where you still have some idea of
what's happening to all the data and where it's going :-)

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Saturday, June 23, 2012 2:35 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Fw: Office 365 Re: You Guys make Me Sick

LOL.  Lists?

I have Plain Old Tables (POT) with 220 million rows, joining to other tables
with 200 million rows, with where clauses considering a dozen fields.  It is
called SQL Server.

As we speak I am in the process of importing a CSV containing ~200 million
rows.  As we speak I am also in the process of importing 540 files
containing 500K rows each.

Of course I also have some serious hardware, at least for a SOHO.

John W. Colby
Colby Consulting

Reality is what refuses to go away
when you do not believe in it


On 6/23/2012 2:20 PM, Martin Reid wrote:
> We have lists with millions of items.
>
> We also have some serious hardware.
>
>
> Martin
>
> Sent from my Windows Phone
> ________________________________
> From: Doug Murphy
> Sent: 23/06/2012 19:14
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Fw:  Office 365 Re:  You Guys make Me Sick
>
> Actually you can use vba if you keep the front end on the client and 
> link to the SP lists in 365. I am not impressed that SP lists are 
> limited to something like 10,000 rows. Hopefully that will be upped so 
> some serious storage can be implemented.
>

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com