Solved Form jumping around in records when i field is typed

[dullster]

Hi
As suggested by Mike Krailo your Transactions Form should look like that shown in the attached screenshot.

Except that i only want the information for a check and not a client.

 

[mike60smart]

Except that i only want the information for a check and not a client.

But as mention by Mike the Form dealing with Transactions is wrong. It needs to be fixed.

 

[June7]

If you retain punctuation/special characters just keep in mind that MUST use brackets around names in queries and many code situations.

I agree that the form/subform arrangement makes no sense.

 

[dullster]

I happened to open that form and typed in a few digits. Nothing happened.
I looked at the query source and use 8931.
Yiu cannot use a bound control to search for data.
You have a lot of empty subform records.

But as mention by Mike the Form dealing with Transactions is wrong. It needs to be fixed.

As i said, i want it by Check number not client #

 

[dullster]

All of the items I listed are relatively easy to fix.

Best to fix now.

Not what I wanted to do, but I understand. I will make the changes.

 

[Mike Krailo]

As i said, i want it by Check number not client #

A main form is the ONE part in a one to many relationship and represents one single record in a given table. The MANY in your subform is based off of tblTransactionsDemo right? One client can have many checks/payment transactions. That makes sense. What doesn't make sense is linking a main form by Check# to transaction in the same table that also has the same exact Check# per Amount in the transaction. That makes zero sense but you keep saying you want it that way.

Stated differently, how can one single check# have many payment Amounts? Please explain to us what the ONE side is exactly and what the MANY side is supposed to be in plain English? Right now it's set up as one single check can have many transaction amounts. This is incorrect because looking at your data, the check# column is not unique. The main form has to be linked by a unique record ID or unique client name possibly. The one side must be unique.

Check# 8784 for example has many transaction ID's and is not a unique value suitable for your main form. Doing a simple search on that check number proves that. I can only conclude that you do not under stand how a simple ONE to MANY relationship is correctly created.

 

[Gasman]

1. NO main form should EVER be bound to the same table as one of its subforms.

I would have to say that there can be exceptions.?
The Emulated Split Form does exactly that.

Two forms with same record source prevent writing conflict

Dear friends, I'll keep it short and sweet. I have two forms, with the same record source. Say form A and form B. Form-A is the main form. But Form-B goes into more detail. Both forms are showing completely different fields on it. But once i entered the details in Form-B, close it, and want...

www.access-programmers.co.uk

 

[Mike Krailo]

Good point @Gasman

 

[mike60smart]

Not what I wanted to do, but I understand. I will make the changes.

Hi
I have corrected all of the points I had noted previously.
I believe I have also updated all of the queries that run your Reports.

See if the db now behaves as it should.

Note there may be some objects that do not run as expected.