Search results for query: *

This is difficult to explain, so I'll give an example. I have the following array of file names: Array ( [38] => CP.W.CC.0805 [39] => CP.W.CC.0812 [42] => CP.W.S.0805 [43] => CP.W.S.0812 [66] => IP.W.CC.0805 [67] => IP.W.CC.0812 [70] => IP.W.SP.0805 [71] =>...

Wow, three answers each 1 second apart. Thanks to you all. Taking out the GO's worked perfectly. I'm not sure I understand what you mean. This procedure is to be run from an Access application that allows the user to 'post' an invoice. By design, they can only post one invoice at a time...

I'm trying to do a stored procedure to update data in a couple of tables. I've written the following code: CREATE PROCEDURE procPostInvoice @InvNumber nvarchar(15) AS --SET XACT_ABORT ON --if one fails, they all fail and all data is rolled back --BEGIN TRANSACTION --GO INSERT INTO...

Great! That works. (Except it's querydef, not queries) Thanks!

Can you use a SQL server stored procedure (uses one parameter) as the record source for a MDB (non-ADP) Access Report? Thanks, Rob

Thanks, but that doesn't seem to do it. I tried opening Access first, then opening the mdb file using File/Open and I still get the same effect. Also, the KB article you indicated is for Access 2000. I'm running 2002 (XP) and have the latest service pack. Is this a common problem? Does...

I am using Access 2002 SP-2 (XP) under Windows 98. I'm developing a database that will be shared and I want to enable record-level locking. If one using is editing record X (through a form), another user should have full access to every record in the underlying table except record X. I do not...

I am using Access 2002 SP-2 (XP) under Windows 98. I'm developing a database that will be shared and I want to enable record-level locking. If one using is editing record X (through a form), another user should have full access to every record in the underlying table except record X. I do not...

...that is the difference between the two. For example: A1 = 8:00 am A2 = 5:30 pm A3 = A1 - A2 A3 will be 0.395833333 (when you format it to General) To determine the number of hours elapsed: A4 = A3 * (24) To determine the number of minutes elapsed: A5 = A3 * (24 * 60) etc... Hope that helps.

Have you tried: FAQ181-1309

D'oh! Beaten by seconds...[smile]

I haven't used this, but try: DoCmd.RunCommand acCmdSelectAllRecords

Yes, the column names would be Month01 etc. If you want to do this in the design environment, make the Field say: Month01: iif(Month=1,Amount,0) and similar for the rest. To use if logic in a function like this, you use iif(test,true,false), but within VB code, you use the IF THEN ELSE ENDIF...

I don't know what other fields are in your table, but if you want to subtotal by month on something like a Transaction Type, then modify my earlier query by adding a GROUP BY clause (easiest to do this in the query design environment).

Try: SELECT Amount, Month, iif(Month=1,Amount,0) AS Month01, iif(Month=2,Amount,0) AS Month02, iif(Month=3,Amount,0) AS Month03, iif(Month=4,Amount,0) AS Month04, iif(Month=5,Amount,0) AS Month05, iif(Month=6,Amount,0) AS Month06, iif(Month=7,Amount,0) AS...

Yes, I'd use it in the third query.

Just an aside...I would still recommend you make a unique ID field for your members (a simple unique primary key for each table). So if each of your members has a MemberID field (you can make it autonumber), then you can do the linking on that instead of the name. Imagine the chaos if you...

What's wrong with copying and pasting? Is this something you want to do once, or always have updated?

I'm starting to think I finally found something that really can't be done in SQL... :) Not likely [smile] See if my understanding is correct now. - You have a list of Members in a table. - You have more than 81 members in that table. - Of that complete member list, 81 have either 'A' or...

So, am I to understand that the field [Member's Database].[Recruiter] is empty for a certain number of records in [Member's Database]? If so, that's your problem. The first query is grouping by that field, so all the records that have a blank in that field are treated as one record instead of...