Search results

1) whats wrong with your enter key? What a wall of text! 2) whats wrong with your language, does it really hurt to type proper english? 3) whats wrong with your space key? Indenting code is KEY to keeping it readable! That beeing said... to find the max ID you dont dont have to use a loop with...

still DLookup for conditional formatting feels like the excel way of using a vlookup, which is just plain wrong. AND why on EARTH would you want to add two values that are part of your where clause.... the sum of the two values should only return 1 value.... This seems redonculous!

COnditional formatting is normaly done on the current record, why use a dlookup? Should be easy enough though to make a dlookup dim x as string, y as string x = "CR01" msgbox dlookup("YourReturnField", "YourTable", " [CR#]=""" & x & """ and VcoDispChk = True and VcoInchk = False " Word to...

It has been a while but IIRC there is an option to allow data entry or not in the properties as well as a "not in list" option what to do with the data not existing (ie. open a form to add the new part) In a relational environment any part used should have an ID, period... you can then proceed...

Ik stel voor dat je een links samenvoegende vraag probeert, dat zal zeker helpen Graag gedaan en succes

Wonderfull new feature by MS that is another example of a bad habit, calculated values belong on query level, form or report level NOT in tables

UDF are always, always a hit to performance over anything you can do in SQL .... *** If it is noticable with the power of computing on a desktop now a days on this particular function is a different discussion. As a rule of thumb, anything in SQL over UDF anyday. Try building a Query...

well it depends a little bit. On what type TMP is in this example, if it is an integer type field it wont accept decimals... If it is for example a double, it will. You are right <= 36, shoudl also pickup 35.99

Try english for starters

I have a wonderfull email address for these kinds of mails .... that I open about 1 time every 10 years or so...

This is what a cascading combobox is for, this should also allow you to add a new record if it is not in the list.... If you use a combobox instead of a textbox it is faster, less error prown (users can see both NR and Description for example) and faster since you can hide the ID and fetch it...

"the table field" ... if it is a field in a table... how is it calculated? Fields in tables are stored information, never calculated on the spot ?

not use case? What do you mean? Case is the same thing as IF, just looks different and works a little different (mostly in our brain). To the computer it is the same thing.... You can compare decimals, integers, strings or dates anything you like in both. Does that answer the question?

Why a hidden combobox, why not simply add your PartID to your existing combobox as hidden column and fetch it from there ? As per my earlier suggestion?

You are not outputting your O21 or O21C anywhere from the function... Also your logic is changed from my post, try to think what happens when your O21 = 90 ??? Perhaps for your "brain" if then else and between will work better....

Nice User defined function, that will surely help performance [/sarcasm]

Should be easy to do if you split the finite string into characters Char1: Mid(Yourfield,1,1) Char2: Mid(YourField,2,1) Etc... then for each column simply put a where clause Char1 NOT between "0" and "9" or Char2 NOT Between "A" and "Z" etc etc... dont make it harder than it is. While regexp...

Stealing / copy paste is harder than it looks Select case will return the first answer that is true, >= 92 will always be the highest value.... There is no need in this case to have a >= .... You only want to use the upper ranges here and us < or <= depending on where you want the exact...

Or simply alter your SQL : SELECT tblPurchaseOrders.PartNumber, Sum(tblPurchaseOrders.OrderedQty) AS SumOfOrderedQty FROM tblPurchaseOrders GROUP BY tblPurchaseOrders.PartNumber HAVING (((tblPurchaseOrders.OrderDate)>=DateAdd("m",-6,Date())));

Your query requires your form to be open, assuming it is open your query should work.... have you tried the dlookup solution? debug.print DLookup("PartID", "qryPartsToStock", "qryPartsToStock.ManufID=" & [Forms]![frmPONumbers]![frmPOItems].[Form]![comboManufacturerID]"& _ " AND...