Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

New user - Complicated form.

Status
Not open for further replies.

R00K

Technical User
Dec 8, 2003
79
CA
I'm creating a complicated form that will function like a portal to all of our data. It will allow input and should update fields to give running totals, etc. What I need is to be pointed toward some tutorials and/books so that I can learn this stuff.

Some of the background work is done: tables, queries(thanks to JonFer and this site), some reports (they need work), so really what I want to do is do the form once the right way.

Any direction would be helpful.

Thanks
 
You can try using about.com, they have some access tutorials, and some links to stuff that might be helpful. My main suggestion would be to tinker around with the form yourself, and when you have specific questions, regardless of how simple, just ask them here. People are usually pretty prompt about giving replies.
 
Thank you for your reply.

I will check about.com. I've done some casual searching on the net already.

I started with making my form tabbed with 3 tabs - 1 for each table and text boxes that would update the data so the user can see the changes their data made on the whole.

The 3 tables are transactions (deposits, withdrawals, description, date, etc), profitandloss (gain, interest, dividend, FTW, etc) and Fees(brokerage fee). All 3 tabs impact "balance" which is a running total. The user will also see their "commission" and other info for different date ranges. The users will also need to open and close account, edit client information, track pay, and other.

I am wondering if I am choosing the most appropiate design or if there are better more efficient designs. My previous question should have been more specific to design suggestions. The DB is normal - I did sopme reading on that - but I don't want 255 fields, a slow interface and something I will have to explain and re-explain to users .[bigsmile]

Thanks again.

 
I should add that I am using Access 2003 and that I will need to produce client statements without navigation on the printouts.

I am going book shopping tonight and let the forum know what I find.

Cheers.
 
Hi r00k,
Sorry I couldn't be of more help, its somewhat difficult to offer design ideas without a more concrete grasp of the data and the way it will need to be used. hopefully the forum can be of help to you with future questions you may have.

Jimb0ne.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top