How to Clear Form Controls for Next Entry

[bloukopkoggelmander]

Hi there FishVal

Thanks for getting back to me. Right first here are all the points you were mentioning of why it would not work:

The query is a crosstab query (crosstab query: A query that calculates a sum, average, count, or other type of total on records, and then groups the result by two types of information: one down the left side of the datasheet and the other across the top.).

The query is a SQL-specific query (SQL-specific query: A query that consists of an SQL statement. Subqueries and pass-through, union, and data-definition queries are SQL-specific queries.).

The field you are trying to edit is a calculated field (calculated field: A field, defined in a query, that displays the result of an expression rather than displaying stored data. The value is recalculated each time a value in the expression changes.). In this case, you may be able to edit the other fields.

The query is based on three or more tables and there is a many-to-one-to-many relationship.


Also , a bit of a breakthrough. I have spoken to some more cleverer programmers than me and I have been informed that Referential Integrity has not been set up on the AS400 I have my links set up to. So we are going through some literature now to see how to do this . I will get beack if we do get the answer to this. Speak again very soon.....

[bloukopkoggelmander]

Right, unfortunately I am going to have to back track now. I will need to go back to having an unbound form. I will now try using recordsets to accomplish what I need to do, but not sure how this works(recordset s).

This is due to the reason that the nessecary changes cannot be made on the AS400 server to make the bound form work .

Right, looks like more studying recordsets now....

[NeoPa]

I think it's fair to say that this thread has a number of good answers embedded within it for various scenarios related to clearing Form Controls.

However, for me the one big lesson is that when trying to develop code of any sort it's most critical to deal with errors a step at a time.

Here, the OP, for reasons of their inexperience at the time & no criticism due for that as we were all there once, is trying fixes for various things as and when an idea either occurs to them or is suggested. This is a recipe for disaster, as clearly illustrated by the painful progress this thread shows.

Separate all individual problems and always fix one before proceeding to the next. The chance of one muddying the waters for others is just too high. It's also very tiring when skipping from one item to another when things aren't working.

Keep your discipline and attack the problems in an orderly and logical way. That way the pain and confusion is kept to the absolute minimum.

In a way, our (Bytes.com) insistence on one specific technical problem per thread can help members to keep to this.