Feb 26th, 2012, 04:50 AM
Is it efficient for me to have 1 table per user account? rather than 1 table many user many columns.?
Feb 26th, 2012, 05:04 AM
Re: Creating tables
Multiple copies of a table is not efficient. It makes coding and maintenance much harder, and is likely to increase the storage space needed.
For similar reasons (but to a lesser degree) multiple columns is not good either - what you should be aiming for is multiple rows (in this case one row per user account).
(2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015) . . . . . . . . Hitchhiker's Guide to Getting Help at VBForums
Classic VB FAQs (updated Oct 2010) ...Database Development FAQs/Tutorials (updated May 2011)
(includes fixing common VB errors) .......... (includes fixing common DB related errors, and [Classic VB] ADO tutorial /further steps, and [VB.Net] ADO.Net Tutorial).
Tutorial: How to automate Excel from VB6 (or VB5/VBA) .•. SQL 'Select' statement formatter/checker .•. Convert colour number to colour name .•. FlexGrid: fill from recordset .•. FlexGrid: AutoSize columns .•. DB Reserved Words checker
Connection strings .•. MDAC/Jet/ACE downloads .•. SQL Server downloads .•. MZTools (free upgrade for the VB6/VBA Editor)
Click Here to Expand Forum to Full Width
Survey posted by VBForums.