Search results

Your problem may be the name of the text box being the same as the name of the data field. I would ensure the text box object (as distinct from the data field) had a unique name e.g. txtEntryNo, then the control source of the text box might be:- ="Issue-" & [EntryNo] Of course, what Rich says...

Firstly - I strongly! recommend that you avoid the use of special characters and embedded spaces in object names (e.g. names of tables, fields, queries forms, reports, text boxes etc etc) So I would rename the "Entry_No" field to "EntryNo" or EntryNbr or something without the underscore. Apply...

Access supports this with a DateAdd function, but it is not in Excel, as far as I'm aware. If what you've got works.... however, do you need to cater for incrementing the year too, e.g. 01-Dec-06 + 1 month --> 01-Jan-07.

Adding a month is not necessarily "simple"! e.g. what is 29 JAN 2007 + 1 month = ?? 29 JAN 2008 + 1 month = ?? Or are you only ever dealing with the first 28 days of any month ?

NSSQL = "Select * from T_Drug_Receiv_Head where [Entry_No] = " & """" & Txtmax & """" you concatenate the contents of the variable, rather than the name of the variable, into the SQL. Because the underlying field is type Text, eyou also need to encapsulate it in quotes. BTW - are you certain...

It is Latin for "so" or "thus". There are numerous postulations as to its use, or the intentions of any and all who use it. The one most appropriate to this discussion is

Namliam, Sorry, I wasn't kidding, but it was an error of judgement on my part. It is one of my pet peeves, and it got under my skin at just the wrong moment. For me, reading text with incorrect usage of (you)/your/you're and even there/their/they're causes difficulties, as although they sound...

Try the NZ() function. The default behaviour of this function returns a zero-length-string when the argument is null, or the value of the argument when it is not null. You can over-ride the default (zero-length-string) by specifying an optional parameter to substitute for when null is...

Pmfji.... What Namliam said, without labouring the point, is that you use this wizard to define your Import Specification, and save it (with a name of your choosing). The buttons for this are there (under "Advanced...") in that wizard, if you look hard enough for them. You then refer to that...

A table is inherently an unordered recordset. Once you know that fact, what you are asking does not make sense. I strongly recommend you read This Thread, one of numerous threads where Pat Hartman (one of the forum's resident gurus & MVP to boot!) explains it well. Can you achieve the desired...

Use acViewPreview in lieue of acViewNormal. acViewNormal ==> print. hth regards John.

In query design mode, right click on the line that joins the two tables in question. Choose "Join Properties" from the shortcut menu that pops up. Depending on the version of access you are using, there may be additional options in the next dialogue box, but it should include a choice of...

You need to pass the name of the form as a string. Private Sub Form_Close() If IsLoaded("FrmEnquiry") Then 'note : enclosed in quotes or Private Sub Form_Close() dim frmEnquiry as string frmEnquiry = "TheNameOfYourForm" If IsLoaded(FrmEnquiry) Then 'not enclosed in quotes i.e. a variable...

Ken's script doesn't perform an update operation on RS2. The last update is discarded when the procedure ends and RS2 goes out of scope. This could be rectified by adding rs2.Update rs2.Close between the existing rs1.Close and MsgBox "Done (KenHigg is so smart!)" i.e...

Format(nz([X],"*"),"#.#")

FormatNumber is not an AC97 Function, hence why it won't work in 97. Would this work:- Format(nz([X],"*"),"#")

Readability & Maintenance I find it easier to understand what the intent is, with less detailed examination... are those the *same* three (four, five whatever) controls being set to opposite values on either side of the else? Plus, if you want to add/change/delete one, you only have one line...

Of course I don't know what your form looks like, or what you are ultimately trying to achieve but the below may be easier to maintain... Private Sub Form_Current() dim bVisDataPulse as boolean dim bVisCreateU607ST50 as boolean dim bVisU607ST94 as boolean Select Case...

I'm thinking that adding in individual staff member's holidays adds an extra degree of difficulty; unless they are somehow built into this "rota" thingy. Can you paint a bit of a picture? e.g. if I were to guess a it (not including holidays).... Line | Mon | Tue | Wed | Thu | Fri | Sat | Sun...

Im not sure what a "rota" is. Can you please elaorate on that a little. Also, are you wanting to determine the hour (or time) at which a given employee should commence work on any nominated day? Or are you trying to track whether or not individuals actually start, and on time, for every day?