Search results for query: *

You can modify the join properties query design view so that a record is created (with aircraft name, etc.) even if there are no matching maintenance records. This will create a RIGHT (or LEFT) JOIN in SQL view.

The easiest way to create this behavior is an option group with two check boxes in it. The value of the option group will be either 1 or 2, depending on which box is checked. You can set one of them as the default.

The autonumber should reset if you delete all the records in a table and then compact & repair. If some records remain in a table, the autonumber should reset to the highest existing autonumber in that table, plus one.

How far do you get? Have you tried setting breakpoints? I would try adding many parentheses to the SQL statement so that the comparisons are absolutely clear to the compiler and optimizer. Also, I would declare the string variables using more unique names, since "insert" and...

Sorry - don't have any experience with SourceSafe. It sounds like SourceSafe is not installed properly or that you have installed a version of full-blown Visual Basic that is conflicting with the Access/VBA installation.

You need to run the command button wizard again and select the option for opening a form, not running a macro. Select "Form Operations" and "Open Form" then select the name of the other form that you want to open when the user clicks the command button.

>Also by using binary I do not waste tons of space with each record for this flag that is unneeded The easiest way is to use an Yes/No (boolean) data type field for each flag. Otherwise, you will spend too much time writing and testing conversion routines. Neufarth's suggestion of an integer...

What is the source of the binary number? Imported from a text file, a SQL Server query, user input in a form? As far as storing the value, the field in your table just needs to be designed as a Number data type with a field size (Byte, Integer, etc.) that is sufficiently large to accomodate...