Not sure where to put this question.

B

Bob Quintal

=?Utf-8?B?aHR0cDovL3d3dy5iZWF1dGlmdWxtaW5kcy11cy5jb20=?=
<http://[email protected]>
wrote in
I am intermediate when it comes to building a database.
Unfortunately, what I need either goes beyond my knowledge or
I just forgot how to do it.

I am building a db for my business. The db is not online, just
for me to keep track of items, costs, expenses, so on and so
forth. Right now I am trying to tie in a totals box for the
following:

Sale of the item - the % of our commission - expenses = what's
left

As simple as that sounds, I don't want a lot of subforms and
would rather do it in a dlookup, or any other way that
wouldn't clutter the design view.

The expenses are in several different tbls. (gas, copies,
telephone calls, etc.) The information I need for each will
conflict if I have create an query.
The fact that expenses are in several tables is the root of your
problem. Becaiuse of this, you'll need to build an UNION Query
then a summary query based on the union query, then you could
use a DLookup() function to return expenses.
 
G

Guest

I am intermediate when it comes to building a database. Unfortunately, what I
need either goes beyond my knowledge or I just forgot how to do it.

I am building a db for my business. The db is not online, just for me to
keep track of items, costs, expenses, so on and so forth. Right now I am
trying to tie in a totals box for the following:

Sale of the item - the % of our commission - expenses = what's left

As simple as that sounds, I don't want a lot of subforms and would rather do
it in a dlookup, or any other way that wouldn't clutter the design view.

The expenses are in several different tbls. (gas, copies, telephone calls,
etc.) The information I need for each will conflict if I have create an query.
 
T

Tony Toews [MVP]

http://www.beautifulminds-us.com
As simple as that sounds, I don't want a lot of subforms and would rather do
it in a dlookup, or any other way that wouldn't clutter the design view.

Subforms are well, well worth using. They may "clutter" up the screen
but they solve a lot of interface problems.
The expenses are in several different tbls. (gas, copies, telephone calls,
etc.) The information I need for each will conflict if I have create an query.

I'd suggest having one table for all your expenses with an expense
type with a join to the expense type table.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top