Search results

Assuming table name tblTable, name field FullName, and new field called Status, UPDATE [tblTable] SET [tblTable].FullName= (Trim(Left([tblTable].[FullName],InStr([tblTable].[FullName],"(")-1))), [tblTable].Status = IIf(InStr([tblTable].[FullName],"(NS")>0,1,0);

Tbl-People PK-PeopleID Document1 (y/n) Document2 (y/n) Document3 (y/n) Tbl-Documents FK-PeopleID PK-DocumentID (Auto) Document1 (y/n) Document2 (y/n) Document3 (y/n) You have a problem with repeating documents in fields. Basically, with your system, you have to re-design the table to add the...

Actually, he should have two tables based on the information given. Of course it's still an oversimplification of a typical market transaction process, but the reasoning is as follows. An ITEM can have ONE description. An ITEM can have ONE location (at least, based on your own process) MANY...

Actually, you shouldn't have a field called 'Balance' in the table, as it is a calculated field between two other columns. When I first read your problem, I thought you meant query. If you want to have a Balance field in the table, then you have to use an Update query to conduct the...

or even... Me.Text1.Value = Me.OptGroupName.Value You don't have to add the .Value, but it is always wise to explicitely show properties rather than use the imiplicit default. By the way, the code should go in the OptGroupName_Change event.

How about... Balance: [Budget] - [Total Expenditures] Make sure this field occurs AFTER the Budget and Total Expenitures fields in your query.

Actually, Dwight brought up a point, although he incorrectly said my version was correct, which it is NOT. When I gave the answer earlier, I did not consider whole numbers, which of course should NOT be rounded up given your example (for instance, 1.0 should NOT round up to 2, etc.) Sometimes...

You will actually need two queries, one to get a count of items the customers purchased, and another one to give you the categories. I'm not sure if you want a count of the categories, or a return of the types of categories. IN any case, here is the query I came up with SELECT...

Here is the Microsoft site answer to "ASP Returns 'Operation Must Use an Updateable Query' Problem" Microsoft Answer to Problem

Cdate should work, IF the text field is a valid date format. For instance, "Oct 13 2005" is a valid date field, but "Octo 13, 2005" is not. The best way to check is to create a query like so: SELECT IsDate(myTable.CurrentDate) AS DateCheck FROM myTable If DateCheck returns false, then...

2 megs zipped is kind of large... can you just copy the tables, query and form in a test db, zip that and post it? Bandwidth costs, you know... ;)

Do a SELECT query based on this filter: trim(left([Addres],3) = "ST ")) OR trim(left([Addres],3) = "ST.")) In the first condition, notice that ST is followed by a space. This should identify all the St prefixes, including those with or without the period, in the first three characters of...

The autonumber does not show up until you are actually adding new data into the field. A workaround can be to create a boolean field that remains hidden from the user. When the user inputs new data (say, with autonumber field 55), and you want the form to show 56, then in the events that...

Dev Ashish, probably the best Access guy on the web, posted this method for creating an Autonumber field that starts at a certain number: http://www.mvps.org/access/tables/tbl0016.htm

In Access Help search field, enter "Create an Access database". Learn the basics here. It is the most efficient method for you to get up to speed for free. You can also google the web with "Learn Microsoft Access" and come up with thousands of links there. The biggest challenge facing most...

Depending on how many fields use the Iif statements, and how many records you are returning from the query, it is sometimes more efficient to use a module. Keep in mind that the Iif statement, which you must use when you do not use VBA code, will ALWAYS analyze both conditions. When you use...

I would go one step further... Duration: (Iif([DischargeDate] > #06/30/04#, #06/30/04#, [DischargeDate]) - (Iif([EntryDate] < #07/01/03#, #07/01/03#, [EntryDate]))

You can run 40, but there are three considerations. 1. Create queries that will return only the amount of data you need. Do NOT create forms or reports that bind to tables, just efficiently designed recordsets. 2. Do not link the tables. Use the ADO object model to create recordsets, making...

Why not... =(DateDiff("n",[StartDate],[CompleteDate]))\60 & Format((DateDiff("n",[StartDate],[CompleteDate])) Mod 60,"\:00") All that you are doing is replacing the field name with the calculation in the main query.

You don't need anything complicated. Int(MyNum) +1 I assume you have positive numbers only, as -1.4 becomes -1, etc.