Basics of Unbound Forms???

[bjdobs]

I seem to be behind a slow moving street cleaner creating a huge cloud of dust ... I develope and maintain client server apps under Progress and also have worked with Foxpro in a past life ... can someone please point me in the general direction of online material explaining how to do unbound record access using find, update?

In Progress there are several constructs that provide access to data;

This statement will provide one record for read (no-lock) or write (exclusive-lock)

find first | last <table> where <expression> no-lock | exclusive-lock

This statement will iterate through a range of records

for each <table> where <expression> exclusive-lock | no-lock

In looking through the online help it would appear that access does allow these types of constructs in a round about way ... first defining a container object to hold the data then define an sql statement then finally calling the statement. I have yet been able to get the examples to work in part due to the dim foo as database not being recognized.
what am I missing?

 

[DonQuichote]

In unbound forms, you can do a lot with SQL, but generally recordsets are faster. If you decide to use SQL, look for parameter queries in the helpfile. Parameter queries allow you to use 'similar' queries without parsing them each you use them.

If you want to use recordsets, you can work directly with tables and indexes for fast searching. You'll need the following objects (assuming Access '97 and therefore DAO, if you're using Access 2000 you can still use DAO but you will have to set a reference first):

Database, TableDef, QueryDef and Recordset

Look for these in the helpfile. There are some examplesin the help as well. For fast searching, look up the 'seek' method of the recordset object. Also take a good look at the type of the recordset, as this can have a major influence on performance.

I think this should take you busy for a while...

Good luck!

 

[danvlas]

You seem to be trying some DAO code (for Access 97) in an ADO database (Access 2000 or XP)

Open any module, go to Tools-References and set check Microsoft DAO 3.6. Object Library.
Then fully qualify the object:

Dim foo As DAO.Database

Regards,

Daniel Vlas
Systems Consultant
danvlas@yahoo.com

 

[bjdobs]

Thanx for the hand up