I totally disagree with the home pages first statement on using MSAccess as a frontend to a SQL Server backend!! (does the host on this board know about the capabilities of MSAccess and the tricks to make MSAccess a GREAT frontend to SQL Server?) It's statements like the first sentence I read on this board which really sadden me because it shows a lack of knowledge on techniques and MSAccess. As I've stated countless times - it's all in how you design the table structure and how you write your code. I've proven this with MSAccess as a frontend and SQL Server as a backend. MSAccess as a frontend and a backend SQL Server was used in several programs I developed to keep track of all of the Midwest Energy conservation programs (about 10 gig of data)! The application wrote 4000 checks each month totalling over $500,000 and automatically balanced to the bank. So if you get an ENERGY STAR rebate check, know that you're getting it from an MSAccess application! I've programmed with MSAccess since version 1.0 and SQL Server since version 6.5 and I can tell you they work as an ENTERPRISE level application! YES - I said Enterprise level application and I'll challenge ANYONE to ANY application to prove it!! I really hate to see boards and hosts like this one which think you can't use MSAccess as a frontend as an Enterprise application or shouldn't use it with SQL Server. I've done it countless times and I can prove it works very well! Lack of knowledge is no excuse for discrimation or writing things you're not 100% sure about! I could've written the application in Foxpro or Powerbuilder or Visual Basic or C with the same results (it would've just taken me 5 times as long). But I wrote it in MSAccess (using unbound forms which is a technique I think was forgotten when the home page was written.) Again, if you want to challenge me, I can, have, and will prove it! I would recommend the host of this board change their opening home page to something more accurate in regards to MSAccess and SQL Server!