Replies

You could also do it this way, if you didn’t want to have to bother with combo boxes.

here is a basic example

Hi

Probably the easiest thing to do is to create two controls.

A combobox and a textbox.

Create the combobox so that it contains two columns, 1 the code and 2 the description.

Now…make sure the code is the column that is first in the combobox and make the second column (containing the description) a width of 0.

Now set the textbox so that it is locked and disabled. Set the datasource of the textbox like so: =comboboxname.column(1)

I will follow with an example.

J

If you were to use a ‘custom form’, I would open it as a dialog form using the docmd statement (it is one of the options), look it up in help. This should solve the problem of losing the focus for the appropriate control on the originating form (if it doesn’t, you can very specifically set the focus to the appropriate control in the line after the docmd (the code in the main form halts if you open a form as a dialog form until that form is closed).

Jayden

I know that it isn’t an answer to your problem entirely…but I wonder if you could use standard message box (with OK button), then use the ‘sendkeys’ command to send a carriage return to the msgbox? Don’t know if that would work.

I would say that it is easier to create a seperate form than do this though. You could create a seperate ‘generic’ form for this purpose, passing whatever message you want displayed in the ‘openargs’ argument for the form. This means that you could have the one form for many purposes. Just an idea.

Cheers

The program that is stand alone that you are talking about is an Access program…not VB or C++ or something?

On a partly unrelated topic…but why don’t MS actually change this in Access when it automatically creates controls. It seems like it would be a relatively simple change (famous last words)?

ADDED: Sorry, this is a bit out of context at the bottom of the thread…I am talking about Access automatically naming control names exactly as their underlying Control Source.

Try

DELETE tblA.*, tblA.PrimaryKey
FROM tblA
WHERE (((tblA.PrimaryKey) Not In (select ForeignKey FROM tblB)));

Where PrimaryKey and ForeignKey are the fields that you would join on.

Not an entirely perfect solution…but why don’t you use MS Exchange / Outlook? You would set each computer up as a resource?

I might be oversimplifying the solution, but it also might prevent a lot of hassles?

When you say that all your other controls ‘refuse to work’ what exactly is happening with them? Are they just not responding (i.e you click them and nothing happens) or are they giving an error message?

If they are giving an error message, what is the message and is it the same for each control.

What are your other controls trying to do (ie. what code sits behind them?).

Cheers

Jayden

In answer to your second question:

Add the two tables to a query

Create the Join
Right click the join
Select the join that shows all records from B and only matching records from A

then..

Add to the query the joined field in table A, and give it the criteria of IS NULL (you will also want to add any field you want to see from table

viola

You should get a result set returned that gives you all records in B, that do not exist in A

J

I’ve seen strange things happen like this when a required library is not installed.

If you go into the VBA window, then TOOLS –> REFERENCES make sure there are no missing references.

From recollection, a very common problems is DAO 3.5 and DAO 3.6

You may find that there is a reference to DAO 3.5 or DAO 3.6 , when the other doesn’t exists.

I don’t know why it affects the FORMAT or LEFT functions, but I have certainly had this problem.

Let me know how you get on.

Jayden

Hi Shane

Thanks for your reply. Unfortunately I no longer work at the place where I was doing this … so can’t test out your theory…but thanks anyway.

Jayden

You will need a field in the underlying table.

Then you will want to add a textbox on the form bound to that field. You would probably want the textbox enabled = false, to stop users from manually entering dates.

Then use the BeforeUpdate property of the form / record to set that text box to the current date.

Cheers

Jayden

Just a thought out of left field, which actually has nothing to do with the database being in SQL Svr or JET.

I have had a problem with ‘erroneous’ locks from a form – when the form uses a recordsetclone of the forms recordset. Unfortunately I have never found a ‘cure’ for the problem.

On another tac. Can you go into SQL Server and actually see who is locking what and when? This may give you an idea of what SQL Server is doing at least.