Search results

Since this is a calculated field, Date() > Expiration, this should be done in a query. SELECT FirstField, SecondField, Expiration, Status: GetExpStat([Expiration]) FROM YourTable Public Function GetExpStat(ExpDate As Date) As String Select Case DateDiff("d", Date, ExpDate) Case...

There is a Wizard that starts when you add a combo box which allows you to select an option to have the result look up a record on a form. Use this. You can then change the recordsource to only return DISTINCT results, so you wont get the duplicates. PBaldy, you beat me to it. :D

What was the problem and the fix. Please post so the next person searching for connection string issues can perhaps use your research. That is what we are all about here. :D

Well, here are my thoughts. Change this function to a SUB and call it from your form. Don't add the records in another routine, do it in your SQL Statement and add a BatchAddNum field to your AssignedBatches table: Dim LastAdd Long LastAdd = DMAX("BatchAddNum", "AssignedBatches") strSQL =...

Shouldn't that be [Name]?

Wow, I've been looking at your code and it is confusing. Is the end-goal here to return the BatchNums that have been newly entered into the AssignedBatches table? It appears you first are getting #n of the batches in the MasterBatch table that are not in the AssignedBatches table. Then, you...

MDAC = Microsoft Data Access Components Go here: http://www.microsoft.com/downloads/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&DisplayLang=en This will allow you to check the version that you are currently using as well as check the version of some other components. It also...

Spanish title. No difference. I'm guessing your user had an MDAC change ...? Reload the version of MDAC you company currently uses.

I've always found setting the Tag property useful.

Try changing: s.OrderID FROM Orders p To p.OrderID FROM Orders p in both places Just to let you know, this will give you customers who have placed orders in 1996 AND 1997 ... not OR ...

Hmmm ... why are you using DLookUp? UPDATE Table_A SET Address = Table_B.Address FROM Table_A INNER JOIN Table_B ON TableA.ID_Number = TableB.ID_Number

You can leave the BE in 2002, but it may be easier to maintain going forward if both are in the same version. Setting a password for the MDE is optional and can be done in the MDB or the MDE.

Try: Year(YourField)

I'm guessing you have this query defined as a VIEW since you are returning the TOP 100 PERCENT with an ORDER BY clause. Lets call it YourQView. You are going to have to add the fields you need in the payrollers1 table to the SELECT part of YourQView. Those being the ID fields. From where...

If Username is to be a calculated field, then do not store it. Just alias to calculation in a VIEW, then reference it where you would your table. Create View YourView AS SELECT Forname, Surname, Forname + '.' + Surname AS Username FROM YourTable But, if you absolutely want to: UPDATE...

Try: UPDATE InventoryComponent SET QtyOpen = 31 FROM CompanyPurchasesDetailsComponents INNER JOIN InventoryComponent ON CompanyPurchasesDetailsComponents.PackageItem = InventoryComponent.PackageItem WHERE (CompanyPurchasesDetailsComponents.OrderNumber = '12345-1') AND...

You can only debug in the MDB version, since the code will be in its compiled form in the MDE, hence, you can't view the code. If you have an error, you will need to replicate the error in the MDB version to be able to get to debug mode.

Check out the CDate() and Format functions.

Need more detail, please.

What datatype is [Cylinder Number]? Have you tried stepping through the code and checking the values? Change to this: SqlStr = "SELECT * From tbl_Delupdate Where [Cylinder Number] = '" & Stringy3 & "'" Debug.Print SqlStr Set rs = db.OpenRecordset(SqlStr) And put a code break on the line...