Search results

As an idea, where you carry out the check on the cell, try assigning the value of the cell to a variable and a) return that in a message box so that you can see what the code views and then pass that variable through the check. ie: Instead of: If...

Could be horribly wrong but think that if you change Private Sub cmdCellCheck_Click() to Sub cmdCellCheck_Click(ImportFolderName, ImportFileName) Dim objXL As Object, x On Error Resume Next Set objXL = CreateObject("Excel.Application") With objXL.Application .Visible = False '...

shot in the dark try Val(txtWidth)

have a list of the teams and use that to force a result. Easy way. Create a second query linking the list of teams to the results of the current query. Select the link to show all reocrds of teams and those that match in the previous query.

How about using the module to write the data of the 4 identified teams to a table then link the table to the report?

If you are using 2000 or newer then try dim rs as DAO.recordset

Mike, Sorry I wasn't clear enough in the previous message. Here are some rules: [] are used to enclose fields. If the field name is a continuous string then you do not need it, but if there is a space then you do: eg: tblAPPLICATIONS.MyContinuousFieldName {OK}...

Note. I am not taking the outgoing ID in any of the example. The code I sent uses the following: Table: COR_Log, FIELD: ID {This ought to be the ID of the INCOMING order} Table: Main_Table_Name, FIELD: IncomingFieldID {This is the field in the main table that ought to show which INCOMING ID...

try rsDat.Edit rsDat("syncDate") = varNewDat rsDat.Update if that doesn't work then there is the long winded method: rsDat = Currentdb.OpenRecordset("tblSync") rsDat.MoveFirst Do rsDat.Edit rsDat("SyncDate")=varNewDat rsDat.Update rsDat.MoveNext Loop Until rsDat.EOF = True HTH

Guessing (or is it hoping??) that you have an ID field in COR_Log. Next presumption is that in the main outgoing table you register the ID field of the incoming instruction. So long as this is the case then you run a query showing all ID numbers in COR_Log that do not exist in the main table...

On the first IIf statement remove the bracket .[DATE RECEIVED])<= Iif This is because the bracket after DATE RECEIVED is closing the Iif statement which is not what you want. { IIf(test, true, false) } HTH

How about calling the code within Excel Sub Auto_Open() then when it is opened the code will run automaticaly?

As with others the firewall at work will not allow email attachments. zipped and 1.24 mb sounds way too big for a dev db. Goto Tools and compact the database and then zip it and post to the forum. If that is still too large then remove unnecessary data ie if you have 200 items in the tools...

>dateadd("h",-12,now()) HTH

Suggest that you check that the reference libraries are the same

Try the plain close command: DoCmd.Close DoCmd.OpenForm "frmWelcome"

Sorry do not know XP hence why do not recognise error message. 2k goes wrong on Recordsets if you have not loaded DAO3.6 reference library

What version of access are you using? Also try MyQD.close just before set MyRS etc.

After: Dim MyQD as QueryDef Set MyQD = Currentdb.CreateQueryDef("TestQuery",A$) Add: Set MyRS = currentdb.openrecordset("TestQuery") {Or whatever name you have used in CreateQueryDef} and carry on as normal HTH

I think that set rs as recordset indicates that you are using an existing query. Try creating a query and then setting the SQL value to your string ie: Dim MyQD as QueryDef Set MyQD = Currentdb.CreateQueryDef("TestQuery",A$) HTH