Search results

What protocol is it trying to "follow" when it can't?

If you can do it in two queries, and they have the same fields, just use UNION ALL to put the two queries together, would be the easiest. SELECT Field1, Field2, Field3 FROM Table1 Where Something UNION ALL SELECT Field1, Field2, Field3 FROM Table1 Where SomethingElse

If it is a date field, can't you order by City, then date descending?

you need something like this: SELECT COUNT([This Field]) as HowMany, [Some Grouping Field] FROM MyTable WHERE some criteria GROUP BY [Some Grouping Field] Or use the query designer and hit that totals (greek backwards E thingy) and do it visually. Basically

I am assuming syringe 1you are matching to Syringes and needles. It would appear from this limit view of your data, and assuming I am correct in the above sentence, a cross reference table saying syringe 1 = Syringes and needles, syringe 2 = Syringes and needles, syringe 3 = Syringes and...

Create a fields that apply to both. Say use Last name for Company name when looking at a company record. You can even create two forms, one for companies, and one for people, and filter on your type field. Then you won't need to manipulate the field labels even.

Anyone know how to make s Access DB single use? i mean only allow a single users at a time, without changing each persons Access to Exclusive from Shared? So exclusive at the DB level?

I would keep all the data in a single table (basically) with a TYPE indicator to tell me what it is. I.E. Type = P, it is a person Type = C, it is a company You can then handle it how you want.

Import into a "work" table. Run queries to update the related tables as appropriate.

I agree with you, the tables should remain linked, but for some reason, using a 2003 MDB file, with 2007, the links seem to break on a regular basis. I am not sure why that is, so refreshing the links for each connection works. Maybe because our FE is running on Citrix, I don't know for sure...

I think this is your problem: HA_Seg_Id = @Insurance You have to use something like: ISNULL(HA_Seg_Id,0) = ISNULL(@Insurance,0) OR something likeL: AND ((@insurance IS NULL AND HA_Seg_Id IS NULL) OR (@Insurance Is Not Null AND HA_Seg_Id Is Not NULl and HA_Seg_ID = @Insurance))

Well access is basically saying, I think I should have this record, based on the primary key value I have, but it is gone, so it must be deleted. Have you tried relinking the table?

Different SQL client maybe. Specifying an older one but only a newer client might be available? What does linked table manager say it is looking for? You are relinking the tables after creating the DSN right?

Sounds like it could be a primary key issue. Check that first.

Global ODBC1 As String Global ODBC2 As String Global ODBC3 As String Global ODBC4 As String Function InitApp() ODBC1 = "SERVERNAME" ODBC2 = "DATABASE NAME" ODBC3 = "SQL USER ID" ODBC4 = "SQL USER PASSWORD" End Function Function RelinkTables() As Boolean Call...

If you go into the builder, and functions, can you find the function listed in that?

How about if the [Training Taken n] field is NULL they have not taken it?

Not 100% sure mind you, but your function name and your reference of that function are different in your example. Contact vs. Concat

If you import to a table. Create a continuous form you can filter on your table. I would try the easy one first.

Use the DOCMD.Setwarnings False to turn off True to turn back on