Shall we give up the subform Line Number ?

message from =?Utf-8?B?TGl6YQ==?= on 2 Jun 2004

Hi Access MVP,

My colleague Jeff and I have been working on a form for 3 days. The form is for Inventory Movement Enquiry. There is no table update, just only read from several tables. The enquiry composes of main and subform. These two forms are absoulately unbound. In the main form, there are only 2 key controls, product and warehouse. User will choose product first and it will lead a AfterUpdate to formulate the warehouse combo box. So user will see those warehouse only associated to the chosen product. After the warehouse is chosen, it will lead the warehouse AfterUpdate to pull the transaction history and place in the subform. In the subform we use For Each control and Select .. Case to display all history. So far it is working fine, except we think it would be better to put a line number in the subform for easy reference.

Jeff and I had put up several thread here for how to handle subform with codes. Tom Wickerath passed me a sample code for this. The function itself is working fine. The problem is we do not know how to put together with our codes. We really need help from MVP or should we give up the line number feature.

Many thanks in advance to all MVP experts !!!

Allen Browne replied to =?Utf-8?B?TGl6YQ==?= on 3 Jun 2004

Liza, continuous unbound subforms will not work.

You can simulate them with considerable effort, but we cannot write and
customize this code for you.

Archived message: Shall we give up the subform Line Number ? (Microsoft Access Error Message)