Search results

Try removing the brackets from [Forms].

This example is a bit strained, but here goes: Table tblOrder OrderID PK Table tblOrderLine OrderID PK OrderItemID PK Article Amount Price Suppose you want a grand total for each order: SELECT tblOrder.OrderID, SUM(tblOrderLine.Amount * tblOrderLine.Price) AS [Grand Total] FROM...

Andrew, this should go a long way towards what you want. Yes, it looks ugly. Yes, it could be done without the buttons. Just not by me at this time :D. Thanks go to Steve W for inspiration.

1. Is DepID the primary key for table Dependent? Open the table in Design view and check if there's a key picture to the left of the DepID field. If there isn't, right-click to the left on the DepID field and select "Primary Key". 2. Maybe you're dragging the wrong way. Drag the key field from...

Maybe this example will give you an idea.

Steve was still right about normalization :). You're turning an interface problem into a database problem, which (as you noted) would create a maintenance nightmare. This would be the basic normalized table structure: Table Customer: CustomerID (primary key) Customer Name ..other...

Not necessarily, but that might well be the best solution. You might even use 3 or 4 queries :D. I'd probably use a separate query to do the SUMming, then JOIN on that query. I usually try to put as much in one query as possible, then JOIN on separate (sub-)queries where necessary. Works...

I built a tool to (eventually;)) do that kind of thing (output queries to text files, change the text files, re-apply the text files) but as it is it's only useful for me :o; I should get working on that again :D. I think I read somewhere that V-Tools has a useful search&replace function, you...

Check the order in which tables are imported. If you try to import OrderLine records before Order records while a foreign key is defined for OrderID, you'd get that message. It could also be a duplicate key for a field that has a unique index in SQL server, but not in Access (not likely, I...

Your problem was more "interesting" than I thought :D.. I see some possible problems with your approach. Is the UNSPSC code an account code that never changes? It looks like you can only get at the latest expiration date for a given code by following the complete history of that code. That...

Really. Your question is really vague. Are you having a problem with a report you're trying to create, or do you not know how to create a report at all? As an Access novice: Read up on Database Normalization. As a forum novice: Read the sticky post on asking questions the smart way in the...

Create a form (frmReport) with 2 input fields (txtYear and txtMonth) and a button (btnShowReport). Have all the queries use Forms!frmReport!txtYear and/or Forms!frmReport!txtMonth instead of [input year]/[input month]. for the button On Click event, use something like DoCmd.OpenReport...

Something like: [data field] = Replace([data field], "*break*", vbCrLf)

I don't think you can put that variable in the JOIN clause. Try this: sSQL= _ "SELECT AWI.exact_date, " & _ " AWI.job_number, " & _ " AWI.fitter_name, " & _ " AWI.job_duration, " & _ " fitters.fitter_phone " & _ "FROM AWI " & _ " INNER JOIN fitters " & _ " ON AWI.fitter_id...

Add a column to your query with the following expression: CompleteWeek: Iif(IsNull([CompleteDay]),Null,DatePart("ww", [CompleteDay])) and put it in the 'Group By'.

Have you tried SELECT * FROM Contact WHERE City = forms![CityReport]![City]

Maybe the columns are disabled?

That depends. Can you post a bit of sample code?

Have a look at Make-Table Queries, this may be just what you need. On the other hand, you may only think you need to generate tables on the fly :D. Not enough data :). I think those examples are straight SQL. What do you think of as 'straigh SQL'?

0. Backup your databases! 1. Make sure that there are no duplicate IDs in the old and new database. If there are, you may have to change those before you import the old data so the values won't conflict when the data is merged. 2. Change the data type of the new ID field from AutoNumber to...