Neil,

No offence intended, but in my opinion the questions you are asking are not specific enough for this forum.

In other words, what is perfectly clear to you, because you know your scenario, becomes gibberish to me.

If you could break it down into smaller chunks and be a bit more precise in what you're trying to achieve, I'm certain youll get answers from lot's of very able people.

BR

Peter

>I am after some advice on a new application I am designing. We are currently using an application supplied by a software vendor. Amongst other things it is a form which sits on top of a table. I dont have access to the source code for obvious reasons but I would like to add more data against each record. Therefore in one of the fields I have put a trigger which means if someone inserts a value it will open up my new form which will allow the user to add more information against my new table.
>
>Therefore I now have my own table with all the other information in. The two tables will be related with a key field called artikey.
>
>When I open my form it passes the artikey of the current record I am on from my original application to the new form of my new application which is great. I want to utilise my key field to see if any other information is present in my new application. Therefore if there is information it will display in my form.
>
>I have a couple of questions:
>
>Should I bind the information in my new table to the form or should I use the artikey from original application to search my new table and then display in the form?
>
>When printing shall I print the information from the form field values or SQL a cursor with the information and then print?
>
>Also in the past if the advice is to bind, I have edited a field on a form which will update the record in the table as I am typing. How can I stop this so that it only updates the table when the user selects save?
>
>Any advice would be greatly appreciated.
>
>Many Thanks