JWColby
jwcolby at colbyconsulting.com
Fri Apr 27 15:33:27 CDT 2007
In playing around with the VB Express I discovered that you can reference an Access FE in a dataset. Doing that allows you to see not only all linked tables, but also all of the queries in the FE. Theoretically this will allow me to build, save and use queries there where I am comfortable until such time as you guys teach me how to build queries inside of VB.Net One thing I am still struggling to figure out is how to move a table from an MDB to SQL Server Express. I have one specific table which is causing heartaches in Access. It uses memo fields and there are LOTS of "locking issues" when users are trying to edit / add these memos. This is a key table, where the user adds dated notes about the claim, so users are in there viewing old notes and adding new notes about phone conversations and other stuff. Microsoft's party line is that these locking issues are often caused by the way memos are stored in pages on the disk and how JET locks these pages during edits. Thus I believe (hope, pray) that if I move that table out to SQL Server the locking issues will go away since SQL Server handles such things entirely differently. A related benefit is that the BE will slim down considerably. These memos constitute well over 250 megabytes of data in a (consolidated) 700 mbyte BE. I could of course simply build the table by hand but I would really like to "just move it", data and all. John W. Colby Colby Consulting www.ColbyConsulting.com