Search results

I use @@IDENTITY

Did you try replacing your last "AND" with a "WHERE"?

Dude...if only you scroll down the page!!!!

So I guess no one know the answer?

You mean by setting the recordsource? There really should be a book about what's faster than what in Access....

This one here: http://www.experts-exchange.com/Databases/MS_Access/Q_20296802.html Or this one here: http://www.kbalertz.com/kb_194206.aspx Faster in terms of least CPU cycles required. Any suggestion/comment is welcome.

dlookup("Customer_Name", "Customers", "ID=" & CustID) I greatly appreciate it.

Really? But I don't have a recordset setup yet. I mean, DLookup is slower than "init a recordset, make a connection, open the recordset, do a search and then read off the result"?? :eek: Also, when you said recordset, are you referring to ADO or DAO?

What's the least CPU-hungry way of reading a certain value from a table? Any other way better than DLookup()?

Now it only takes 6.348 seconds (averaged over a few times) to go through the same changes (changing one field of each record)....but applied to 120,000 records. Definitely a lot faster. So I take it that recordsets are only good for small number of records?

I'm now running an actionquery... (spent the whole day looking for ways to improve it...) It's now sooooo damn much faster.

I'd love to know how to do that....inserting to a "different" table (different from the original source, T1) with the same record set. Any links would be extremely appreciated.

Maybe, maybe not, depeding on how Replace was implemented.

Thanks for the input...that's kind of strange, because within the loop, the field is still only being referenced the same number of times. Anyway, I'll give it a try. Also, I found a problem with it today: Say I have a recordset that has 3000 records. And the do while loop actually loops...

Hum....so what exactly do I need to refresh here? I'll go to Options and see what I can find... Both queries are run by (and inside of) some VBA codes.

Can I make the operation time of the Do While loop shorter? Currently, on my lappy (PentiumM 1.7GHz), the loop takes 6.5 secs (average) to go through 480 records... Set fieldObject = rst.Fields(changeField) Select Case changeOperator Case "Add" If fieldObject.Type <=...

T1 holds the current (up to date data), T2 holds all the data that ever existed...including the newly changed/updated ones. It's not the insert that takes time, it's the Update (or more specifically, the rows that got updated) that takes time to show up.

I have two tables (T1 and T2, say). I update records in T1 using recordset (ADO). Then (immediately) I do a "INSERT INTO T2 SELECT....blah" query (ADOdb.Command), basically copying the updated records from T1 to T2. However...There seems to be a delay between "After the recordset update...

Thanks for the pointers, Pat. I'll look into it right away.

40 records is a limitation, but I guess you can add more if you want. Do you have resizeable columns and columns sorting and repositioning? There's also no real reason for me to re-invent the wheel (the datasheet) just because of a small issue. (and it is a small issue, just one that I can't...