Search results

Then you're sorted? Glad to hear it. Welcome to AWF.

Hi Your with block seems fairly redundant anyway - you're making explicit references to the recordsets each time anyway. :-) If I'm understanding your requirements - you're attempting to add the new row too often. This assumes that the tables and recordsets are appropriate to the definition...

I have no <hic> idea what you could mean.

Yes - for what it's worth I would recommend it in a proper implementation. To be fair though, I'd use a dedicated database object variable if I was doing this for real. Implicit With block objects are all well and good - but there's no getting around neat error handling. Dim db as DAO.Database...

No worries.

Hi Something like: SELECT T.CoilSerialNumber, T.DateReceived, T.CoilWeight FROM tblReceivedCoilHistory T INNER JOIN ( SELECT T2.CoilSerialNumber, Min(T2.DateReceived) AS MinDate FROM tblReceivedCoilHistory T2 GROUP BY T2.CoilSerialNumber ) X ON T.CoilSerialNumber =...

Oh there are just soo many questions. ;-) First of all the purpose. You're copying a table from the front end application into the back end file? Why would you need to? And why would you need to delete the entire table? Does the structure change each time? Deleting and Appending data, that's...

Depending on the type of security you can pass the username and password as part of the MSXML post - rather than as a querystring (which wouldd manifest as the strPost parameter). But I somehow doubt that is the case - and so you are left with the Post method of the IE object model. I did...

Hello over in Sheffield! This can be problematic, depending upon the comment: "...using a sign on eventually". Ordinarily, you'd just use the MSXML object library to fetch the source content of a specified page. For exmaple the function below. Function FirePost(strPage As String, strPost As...

Hi Without disagreeing with the sentiment of the advice, there are just a couple of little things I'd feel better about mentioning. >> This would be a string and hence very slow to process for joins Yes, short fixed length data types (i.e. the 4 bytes of a Long Vs what 20+ for a sufficiently...

SQL 2008 perhaps? What I did actually mean was the code from the original post that wasn't working. Although, I imagine that it was all the same, except that the SQL has now changed (back to the system tables as opposed to views - well, views behaving as tables to views really)? My point is...

That query certainly looks familar. :-p We'll assume that this is indeed a passthrough (it wouldn't parse in Jet anyway and the name impies as much - though, obviously, there would need to be code subsequent to that which you're showing). Consequently it's irrelevant what "Access" likes or...

I believe it was Access 2002 (at worst 2003) which introduced the Popup property for Reports too. Any version that age or newer would be fine. Without that - you're fighting an uphill battle without much to gain.

I'm not clear on what you're saying as a conclusion. That's essentially what I'd pointed out as a caveat in my first post. You just need to construct the query appropriately to allow for that.

That's fair enough - though ultimately it doesn't change the advice I offered. The criteria needs to be applied either in subqueries or accept that the outer joins will be rendered ineffective by any criteria applied? And the index is still the same issue regardless of what's returned etc.

Couple of questions: You refer to a simpification, is this your actual query? SELECT [Products].ProductID, [ProdSuppls].SupplierID, [Suppliers].Name FROM [Products] LEFT JOIN ([ProdSuppls] LEFT JOIN [Suppliers] ON [ProdSuppls].SupplierID = [Suppliers].SupplierID) ON [Products].ProductID...

I'd say you're looking at the optimum choice for what you're doing.

Well, if you wanted to prevent duplicates, then you would have a unique index on that field in question (TEMP_Lakoach_TnuaID) so you don't need to even check for the record first - which saves more overhead. As you're matching - you need to select as efficiently as possible. FWIW I don't think...

Yeah fair enough. Then the topic of the thread is really Access 2007 Vs Acccess 2003 formats. (Or more precisely ACCDB Vs MDB.) Data wise it's ACE Vs ACE. ;-)

Well yes the first snippet was ADO in response to the question at hand. But I was pointing you to the fDAOGenericRst function (as a replacement for your OpenRecordset). I should have been more explicit. Sorry about that.