Search results

Yes, but it will be difficult! You will need to export as an allowed field name eg PO_Item as Jack Suggested then open the exported file, search for the field names and replace _ with . Not a task to be envious of!

Actually, I have reconsidered as Access does not lik the Domain Aggregate function as default values in tables, sorry. In the controls of your form that you want default values, set their default value to the following. =Dlookup("FieldtoCopy","TableName","IDField = " &...

There are a few ways I would conside; 1. setting the default value at table level as a dmax (if you number your records sequentially) for each field you want a default value 2. Set the values at form level by using the Form_Current() event and screening for a new record 2a Using a recordset to...

Looking at it again, to pass values to a module, pass the values as arguments to that module ie Call ImportFW1Switch (me.optionGroupName) when defining the Sub in the module, Public Sub ImportFW1Switch (Byval intOptionValue) This will tell the module that it is looking for a value passed...

You have just learned a good lesson on why normalisation is so important. Rather than trying to muddle through with your existing data structure, normalise your data as it will cause a lot less headaches. Sketch out what relationships you want between sets of data and try to normalise the...

this line Public subfrmImportSwitchData As Form_subfrmImportSwitchData is trying to dim the variable subfrmImportSwitchData as a custom object Form_subfrmImportSwitchData which I cannot see defined in your code. Are you not simply wanting to define the variable as a form? ie Public...

You will need two fields, one for the AirspaceID that they should have been using and an Altitude field in the events table. You will need to bind the altitude textbox to the (new) Altitude field in the Events table and then set the value dynamically, depending on how you select the AirspaceID...

I see where you are struggling as I could not get the Hex function to work either in your Db, depite the syntax being correct. Have you tried importing into a ned Db and trying again? Youe main form has all the info on that you need so I actually do not see the need for this 'checking' form anyway?

If the altitude for a given airspace does not change, you do not need to store it in the events table (as you already have a reference to it in the Airspace definitions table) but only store the airspace ID in the events table. You would then, in your query, add both tables to the query and add...

Here Cosmos, try this. Nicked your code and it works perfectly. :p

Have you tried them both together? ie Dim R ,G, B As Integer Dim HexR, HexG, HexB

This is the very heart of relational Db design, creating tables that store items relevant to that data and linking the 2. Your initial form structure is no doubt correct but you must ensure that your data structure at table level is correct first. With each ID eg NHS number, Social Security...

Just Dim them without a qualifier ie Dim HexR, HexB, HexG and see if that helps

Cannot disagree with that - nothing better than a bit of stiff upper lip. Anyway, cannot get either to work - but as you say it doesn't matter, I dont have the problem;)

A2000 on Win 2000 Must just be me then :D

So what;) Cheers Mile-O:o

No criticism implied namilam - just that the table name was incorrect in your query that is all and so returned an error when the query was run, not a populated recordset. ;)

No problem. Namilam's method will work well if you only have a few fields to compare. My comment was really for if you have several fields to filter as the SQL becomes horrendously complex. If you need any more help with the Dynamic SQL method, search the forums here but shout iof you are stuck...

It is therefore an ideal opportunity for you to start learning. Once you get to grips with it, you will never (well, never say never;)) go back to using macros.

namilam, The demo has the incorrect table names in the query and so will not return the correct recordset. The query will work, yes, using a self join but the QBE grid becomes complicated and unweildy and the SQL becomes very complex (although it will in theory run faster than a simpler...