appear or add more form inside form , or inserting more textfield inside form

  • Thread starter Thread starter wazza w via AccessMonster.com
  • Start date Start date
W

wazza w via AccessMonster.com

hi

i just need a help for MS Access.
when you have a form, and you need to use label and textfield and all that
stuff.
there's one more things, in Loan we've got split 1 and split 2 and split 3
and so on, when you fill up first split, and you need to press on button
"Insert more Split" it will create another addition of split to the same user.


any suggestion please, by the way, i can make it appearing but i need it to
add more information inside one user or customer and appearing in same form
nowhere else :P~

thanks for your help...

--
Wassim Sawan
Bachelor of Information Technology and major in information systems


Message posted via AccessMonster.com
 
wazza w via AccessMonster.com said:
hi

i just need a help for MS Access.
when you have a form, and you need to use label and textfield and all
that stuff.
there's one more things, in Loan we've got split 1 and split 2 and
split 3 and so on, when you fill up first split, and you need to
press on button "Insert more Split" it will create another addition
of split to the same user.


any suggestion please, by the way, i can make it appearing but i need
it to add more information inside one user or customer and appearing
in same form nowhere else :P~

thanks for your help...

I think what you're asking about is the built-in functionality of the
subform control, with the "split" records going into a related table
being displayed by a subform in continuous forms view. The button isn't
really necessary to add a new record in such an arrangement, though you
can have it if you want.
 
hi again

actually i did try that way, but i didnt like it because when you add more
split, and you want to see the record of one customer , it will show all
customers has same splits.
and in other way, the look of continous form and subform inside form doesnt
look like nice way. when you add more split, you will see form is growing up
and up , but in subform it doesnt look like.


do you have another suggestions? i've seen them in Java built, but i wish if
i can see it in MS Access built

thank you

Dirk said:
[quoted text clipped - 11 lines]
thanks for your help...

I think what you're asking about is the built-in functionality of the
subform control, with the "split" records going into a related table
being displayed by a subform in continuous forms view. The button isn't
really necessary to add a new record in such an arrangement, though you
can have it if you want.
 
wazza w via AccessMonster.com said:
hi again

actually i did try that way, but i didnt like it because when you add
more split, and you want to see the record of one customer , it will
show all customers has same splits.

I don't know if I understand you properly. If I do, if you're saying
that the subform always shows the records for all customers, not just
the customer that is current on the main form, then you didn't set the
subform's Link Master / Child Fields properties correctly. Normally, a
subform will show only those records that are related to the current
record on the main form.
and in other way, the look of continous form and subform inside form
doesnt look like nice way. when you add more split, you will see form
is growing up and up , but in subform it doesnt look like.

I'm not sure what you mean. Most people find the scroll bar of the
subform intuitive enough, but if you don't like it -- assuming you've
got it set up properly -- that's your prerogative.
do you have another suggestions? i've seen them in Java built, but i
wish if i can see it in MS Access built

It is possible, with great (and misplaced) effort, to simulate what you
want by creating a form with a set of all the unbound text boxes you
could ever want, but all hidden until you want to add a new record.
Then you would make a new record's set of text boxes visible, reposition
them on the form, and resize the form to make it "grow". You'd also
have to do all the work of loading and unloading the text boxes to/from
the table yourself, using code. It's far more trouble than it's worth,
in my opinion.
 
mmm

hi again Mr. Dirk Goldgar
i thank you for posting back to me, maybe i wasn't clear what i wanted to
build, the problem is that i am working for loan company and they give me
headache, everytime they want to get somehting new in the program and i am
trying all the best to create it.
so i've created the database what they want and what i can do for them, for
subform i made it like continuous form, they accepted that. and everything is
fine.

i've got one more question. with this database access i will put in different
computers such as 4 computers, and i was thinking that each person has
different data entry, how can i combine them all in one database , in other
meaning i want them all to be in one database in diffferent computers.

thank you for your help.
 
wazza w via AccessMonster.com said:
mmm

hi again Mr. Dirk Goldgar
i thank you for posting back to me, maybe i wasn't clear what i
wanted to build, the problem is that i am working for loan company
and they give me headache, everytime they want to get somehting new
in the program and i am trying all the best to create it.
so i've created the database what they want and what i can do for
them, for subform i made it like continuous form, they accepted that.
and everything is fine.

Okay, I'm glad to hear it.
i've got one more question. with this database access i will put in
different computers such as 4 computers, and i was thinking that each
person has different data entry, how can i combine them all in one
database , in other meaning i want them all to be in one database in
diffferent computers.

If the computers are all connected on a LAN, what you should do is
*split* the database into a separate back-end .mdb file (containing
tables only) and front-end .mdb file(the "application" database,
containing all the queries, forms, reports, modules, and so on). The
front-end contains linked tables that are connected to the tables in the
back-end. The Database Splitter wizard can do this for you (click
Tools -> Database Utilities -> Database Splitter).

The back-end is placed on a server PC that all the user's can access
over the network. Each user has his own copy of the front-end, on his
own PC, and each front-end is linked to the same back-end on the
network, so that all data is stored in the back-end and all users can
see the other users' updates.

For more information on splitting your database, see Tony Toews' web
page:

http://www.granite.ab.ca/access/splitapp/index.htm
Splitting your Microsoft Access MDB into a front end and back end
 
hi dirk

thank you very much for your information and i appreciate that.

sorry about saying that but thanks because you gave me a rough idea and i
tried to change it by my way.
what happened is: i tried to do it same way you told me about but i always
get the error message such as "Subscript out range" and this things didnt
work with me, but i followed an instruction from Microsoft office and made it
like separate file such as
Back_End ----> Open blank Dabatabase, then Get External Data, then Import all
tables Only!!
Front_End ----> Open another New Blank Database, then Get External Data, then
Linked tables, select all tables only, then Get External Data, then import
all queries and forms.
in the end you can use it.

Dirk said:
[quoted text clipped - 6 lines]
them, for subform i made it like continuous form, they accepted that.
and everything is fine.

Okay, I'm glad to hear it.
i've got one more question. with this database access i will put in
different computers such as 4 computers, and i was thinking that each
person has different data entry, how can i combine them all in one
database , in other meaning i want them all to be in one database in
diffferent computers.

If the computers are all connected on a LAN, what you should do is
*split* the database into a separate back-end .mdb file (containing
tables only) and front-end .mdb file(the "application" database,
containing all the queries, forms, reports, modules, and so on). The
front-end contains linked tables that are connected to the tables in the
back-end. The Database Splitter wizard can do this for you (click
Tools -> Database Utilities -> Database Splitter).

The back-end is placed on a server PC that all the user's can access
over the network. Each user has his own copy of the front-end, on his
own PC, and each front-end is linked to the same back-end on the
network, so that all data is stored in the back-end and all users can
see the other users' updates.

For more information on splitting your database, see Tony Toews' web
page:

http://www.granite.ab.ca/access/splitapp/index.htm
Splitting your Microsoft Access MDB into a front end and back end
 
wazza w via AccessMonster.com said:
hi dirk

thank you very much for your information and i appreciate that.

sorry about saying that but thanks because you gave me a rough idea
and i tried to change it by my way.
what happened is: i tried to do it same way you told me about but i
always get the error message such as "Subscript out range" and this
things didnt work with me, but i followed an instruction from
Microsoft office and made it like separate file such as
Back_End ----> Open blank Dabatabase, then Get External Data, then
Import all tables Only!!
Front_End ----> Open another New Blank Database, then Get External
Data, then Linked tables, select all tables only, then Get External
Data, then import all queries and forms.
in the end you can use it.

I don't know why you got the "Subscript out range" message, but I've
heard of the various database wizards giving that message under some
conditions. It's a bug of some sort. But there's nothing wrong with
doing it the way you describe, as that's very close to what the wizard
would do. However, if you set any special properties, options, or
references for the original database, you'll have to set them again in
your new front-end.
 
Back
Top