Search results

I personally like the .adp if starting from scratch. It allows you to do all your server development from within the access environment, and I believe that it is quicker than ODBC, as you are working directly with SQL Server through its OLE DB provider. The forms in an .adp use the ADO cursor...

Jon, If you're developing a new app with SQL server as a backend, check out Access Data Projects (.adp), rather than using ODBC through a .mdb. The .adp file is basically all the access front end components (forms, reports, macros, and modules) and a connection to the SQL Server. It will...

Jon, If you use ODBC to link to the server (in a .mdb), simply query them using the Access Query Grid, as you would any table. You can use these queries as the form's recordset. Marty

Just link the tables using ODBC. You can then use them like linked Access tables. You can use them as a form's recordsource. Performance is generally as good as or better than jet. Marty

Coop, if you get a copy could you email it to me? It would be much appreciated! Thanks, Marty

Yeah, I'd really appreciate it, if it is not too much trouble. Thanks, Marty

There may be a simple solution for this, but I can't seem to find it. How can I make a list box autoexpand like a combo box (i.e. finds item in list as user types) in Access 2K. I have been able to do this in Visual Basic using Microsoft Datalist Controls 6.0, however, I am unable to register...

VBA for Dummies is another good way to get started.

You could also use a date calculation in the where clause of the combo's rowsource property and eliminate the need for the yes/no field.

I'd add a field to the same table that the UserId is located in and make it a yes/no data type. Set it to yes whenever/however you want to determine that the user is an "old user". Then set the rowsource property of your combo to exclude all users that are set to yes. Hope this helps.