Francisco Tapia
fhtapia at gmail.com
Tue Jan 24 23:41:19 CST 2006
John, If you intend to use the access front end with odbc, then I suggest you take a good look at ODBC pass-through queries. if you're going to be using the FE as an ADP then with Access 2003 you can at least call the sproc as you do with ado and then set the combo box's recrodset to the ado's recordset. I find ADPs to be quite fast, in fact I haven't built a classic Access FE in almost 2 years :|. On 1/24/06, John Colby <jwcolby at colbyconsulting.com> wrote: > > I need a "step by step" if you will of moving some object to SQL Server - > combo or form - where the Access query was filtered and the filter won't > work in SQL Server. For example a reference to a control on a form. > > I know that I have to create a SP in SQL Server that accepts a parameter. > How do I "connect" to that query from Access? Is it a n ODBC (or other?) > link, just like a table? Then how do I feed the parameters to the SP out > in > SQL server. > > I am getting ready to do this and am way under prepared for this. > > Environment: > > SQL Server Express 2005 > Access (Office) XP or 2003 > Fes now talking to the SQL Server BE using the standard (ODBC I think) > "links" that the upsize wizard created when it moved the tables. > > The FE seems to work as it did before except slower. Now if I can start > replacing the slow "Access Queries over ODBC" with "SQL Server SPs with > passed params????" I might be able to see what this is capable of. I just > haven't a clue how to move to that "SP with Params". > > John W. Colby > www.ColbyConsulting.com > > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More...