Search results

I disagree with Daherb here. A passenger is a customer, customers come back to order again. So you want to check to see if the passenger has flown before. If not, then you use the NotInList event to add a new passenger. The AS Fullname in the SQL stmt sets the name for the calculated column...

Did you use the Combo wizard to build the combo? You don't want to show the IDs, what you want is to show the names but store the IDs. The RowSource should be: SELECT PassengerID, Surname & ", " & Firstname As Fullname FROM tblPassengers ORDER BY Surname, Firstname;

Did you lookup TransferDatabase in Access help? You will find an example there. That's why I didn't give you more. If you still need more help after checking the Access help, let us know.

Use TranserDatabase.

No, you do not want to join the 2 instances of Airports. As I said your links are from PK to FK. FlightID is the PK in AircraftInfo so its the FK in FlightSchedule. ScheduleID is the PK in FlightSchedule so you should have that as an FK in Bookings. Delete FlightID and replace it with...

You need Interim queries. You create a query on vCars that groups on EECODE and SUMS CarCount. You then get another query to group by EECODE and sums total Hours. Join those two together on EECODE to get one record per employee.

Well you still have repeating groups in your Customer table (Phone, fax, Email). Your CallDetails should be a subform Of Calls, not a subfomr of the main form. You should have a separate form to enter Calls, and use the form you have just to show calls for a customer.

Why would you need to? The SOLE purpose of an autonumber is to provide a unique identifier to a record. It shouldn't matter whether there are gaps or not. Especially if you have related tables, you do not want to change the autonumber or you will create orphans.

This is just a guess, but I suspect the toolbar is based on a table (kinda like a switchboard). It was split out but the form references to it were not changed to the BE.

Getting there. You need to add another instance of tblAirports and link that to DestinationID. I would just use Departing as the field name. Definitely not use DepartureDate&Time as the & is a special character. I'm not sure what TripID is either. the relation from FlightSchedule to tblBookings...

What you quoted makes sense up to the last piece. Though I wouldn't consider that a join table since it contains other data. But I do NOT recommend composite indexes. Its much easier to manage relations using a single PK. You can create multi-field indexes to make sure of uniqueness. Also, that...

When you refer to a object that has spaces in the name, you need to put it in brackets, otherwise Access won't know its an object name. If you forget you get syntax errors. If you don't use spaces, you don't have to worry about that.

I'm confused. The ID department and ID fields are your FKs. The table should have its own PK (an autonumber). If you want to create a unique index on the combination of dept and contact ID you can do that.

This is getting better, but its far from complete. You really need to stay away from spaces in object names. I would get rid of tblTripDestinations and replace it with this: tblAirports AirportID (PK Autonumber) AirportCode AirportName City Country Then your tblAircraftIfno would include...

there may be some limits on report footers. but not sure what else to tell you

That's why I said you need two tables. Looks like Daherb is giving you the same advice.

I explained this inthe other thread. A join table would look like this: tblPlayerAdult PlayerAdultID (PK Autonumber) PlayerID (FK) AdultID (FK) AdultRoleID (FK) This way you link the player to the adult and show the relation.

What's the PK? Yes you need to write code. There is no way you will get the app to do all you want without it.

If you need to zero fill a number you could use a format: =Format(INT(value*100)."000000") If value were 860.00 then the result would be 086000

Airlines don't plan that far ahead. You need to decide how far ahead you want to schedule. You can use loops to add records for specified periods.