Tracking Database

[Howard]

-- We would appreciate your suggestions for a tax database to track
preparation and filing of tax returns.

The basic account information is downloaded from our accounting system. That
would be one table. Then we would need a payment table and a filing
information table?

Actually, we have a tracking database now, but the creator of it dumped
everything into one table. So, it’s very inflexible.

Thanks,

Howard

 

[PC Datasheet]

Howard,

I acn create this database for you for a very reasonable fee. Contact me at
my email address below after the first of the year if you would like my
help.


--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
(e-mail address removed)
www.pcdatasheet.com

If you can't get the help you need in the newsgroup, I can help you for a
very reasonable fee. Over 1000 Access users have come to me for help.
Need a month calendar or 7 day calendar? Need appointment scheduling? Need
room reservations scheduling? Need employee work scheduling? Contact me!

 

[Ken Snell [MVP]]

Recommendations would depend upon the type and format of the data that you
download. In general, your database should have tables for each entity/class
of data (e.g., customers/clients, returns filed, types of returns, etc.).

If you can post more details about your data, I'm sure we can provide some
*free" suggestions to you.

 

[John Marshall, MVP]

Back to the ambulance chasing. These newsgroups were providedby Microsoft
for FREE peer to peer support.

John... Visio MVP

 

[Howard]

Free is good! That's why they have me, a non-programmer!
The data from the accounting system is basic descriptive data: among others
we have account number, title, date opened, fiscal year-end and a field
called tax responsibility code. The tax responsibility code tells what type
of trust: grantor trust, irrevocable trust, estate, charitable (number of
different types) among others.
So, I guess we would need this descriptive data table, a return types table,
a payment table and a filing table? The returns type table would be linked to
the tax responsibility code in the descriptive data table.
Would this run off auto numbers? I thought the account number was unique,
but I understand they can be recycled after a number of years. Also, it's
data type is text, not integer.

 

[Ken Snell [MVP]]

If the account number is recycled, then it cannot be the "primary key" of
the table in which it's used as an identifier -- otherwise, data from
different people would be mixed together over time. In this situation, using
an autonumber field as the primary key (which means that your children
tables would link back via the autonumber field, not the account number
field) would likely be best.

The account number field can be text -- not a problem.
--

Ken Snell
<MS ACCESS MVP>

 

[Howard]

Ken,
Thanks. One more thing. Do you have any suggestions about setting up the
relationships between the tables?

 

[Ken Snell [MVP]]

You'll need to specify some details about the data that you want to
track/store.

 

[Duane Hookom]

Steve,
Is this really you? Are you really this ignorant that you would abuse a
public news group like this?
I find it hard to believe that you would so blatantly advertise like this.

 

[PC Datasheet]

It's much more hard to believe that Arno R and his dimwitted friends John
Marshall and Keith Wilby are allowed to pollute the newsgroups with their
worthless rubbish. Did you ever stop to think how much bandwidth these
idiots are taking up? They don't make any contribution to the newsgroups and
are still permitted to do this!!

 

[Duane Hookom]

I'm fairly sure if you would stop trolling and advertising in the news
groups, these guys won't be using up the bandwidth. They don't reply like
this to anyone else that I am aware of.

It's just you and only you...

 

[PC Datasheet]

You can choose whether you want to believe this or not --
In the past four weeks I have received 31 requests for help from people in
the newsgroups all willing to pay for the help. Most requests have already
been completed and I have been paid for most of them. I am working on the
others and will complete them shortly and have been prepaid on most of them.
There for a while you didn't see me participating in the newsgroups because
I was putting all my time into helping these people. There are various
reasons why these people were willing to pay for the help and in fact some
of them had to with the disgust over Arno R and his dimwitted friends. I
treated everyone with fairness and my fees to all were very reasonable. At
this rate I am much ahead of getting to 2000.

--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
(e-mail address removed)
www.pcdatasheet.com

If you can't get the help you need in the newsgroup, I can help you for a
very reasonable fee. Over 1000 Access users have come to me for help.
Need a month calendar or 7 day calendar? Need appointment scheduling? Need
room reservations scheduling? Need employee work scheduling? Contact me!

 

[John Marshall, MVP]

31 more victims. So if I start posting how much money I make by robbing
banks, that makes it ok to rob banks?

So if you do have legions of satisfied customers:
Why are they not jumping to your defence?
Shouldn't these legions of satisified customers be keeping you too busy to
troll in the newsgroups?

John... Visio MVP

 

[John Marshall, MVP]

More childish rants? I guess you never study cause and effect.

You troll for work : we complain.

John... Visio MVP

 

[John Marshall, MVP]

That should have been "studied".

John... Visio MVP

 

[Howard]

Ken,

We'll track the prep and filing of tax returns: when an analyst has reviewed
a return and sent it to our tax vendor for processing; when tax info has been
sent to the trust beneficiary; when the return has been filed. We'll store
all payments made by the trust which include balances due and estimated
payments. And we'll track filing info: date filed, returns on extension
etc. All this would be for federal and state returns.
We'll have various reports.

Thanks again for your suggestions.

P.S. I'm enjoying all the "trolling for work" comments.

 

[Howard]

Arno R,

I apoligize. I didn't mean to imply that it was enjoyable from your
perspective.

No, the offer did not add to my question. Is it possible to have a forum
where people could advertise their services or request help they are willing
to pay for?

 

[Ken Snell [MVP]]

OK - here are some suggested starting points for tables:
---

tblClients (note that this could also hold other entities, such as
payees, payers, etc. - if you do that, you might want another
table called tblRoleTypes where you can store what role(s)
an entity can have)
ClientID (primary key)
ClientName
ClientAddress
(etc.)

tblReturnTypes
ReturnTypeID (primary key)
ReturnTypeName

tblReturnProcessTypes
RetProcessID (primary key)
RetProcessName

tblProcessorTypes
ProcessorTypeID (primary key)
ProcessorTypeName
ProcessorTypeAddress
(etc.)

tblReturns
ReturnID (primary key)
ClientID (foreign key to tblClients)
ReturnTypeID (foreign key to tblReturnTypes)
(etc.)

tblReturnProcessing
ReturnID (composite primary key with RetProcessID --
and with ProcessorTypeID if more than one processor
is possible for a single process type)
RetProcessID (composite primary key with ReturnID --
and with ProcessorTypeID if more than one processor
is possible for a single process type)
ProcessorTypeID (possible composite primary key with
ReturnID and RetProcessID)
DateSubmitted
DateCompleted

tblPaymentTypes
PaymentTypeID (primary key)
PaymentTypeName

tblPayments
ReturnID
PaymentTypeID
PaymentAmount
PaymentDate
PaymentToWhomID
PaymentFromID
(etc.)


and so on....
--

Ken Snell
<MS ACCESS MVP>

 

[Howard]

Ken,

Thanks very much!

HF
--
Howard

OK - here are some suggested starting points for tables:
---

tblClients (note that this could also hold other entities, such as
payees, payers, etc. - if you do that, you might want another
table called tblRoleTypes where you can store what role(s)
an entity can have)
ClientID (primary key)
ClientName
ClientAddress
(etc.)

tblReturnTypes
ReturnTypeID (primary key)
ReturnTypeName

tblReturnProcessTypes
RetProcessID (primary key)
RetProcessName

tblProcessorTypes
ProcessorTypeID (primary key)
ProcessorTypeName
ProcessorTypeAddress
(etc.)

tblReturns
ReturnID (primary key)
ClientID (foreign key to tblClients)
ReturnTypeID (foreign key to tblReturnTypes)
(etc.)

tblReturnProcessing
ReturnID (composite primary key with RetProcessID --
and with ProcessorTypeID if more than one processor
is possible for a single process type)
RetProcessID (composite primary key with ReturnID --
and with ProcessorTypeID if more than one processor
is possible for a single process type)
ProcessorTypeID (possible composite primary key with
ReturnID and RetProcessID)
DateSubmitted
DateCompleted

tblPaymentTypes
PaymentTypeID (primary key)
PaymentTypeName

tblPayments
ReturnID
PaymentTypeID
PaymentAmount
PaymentDate
PaymentToWhomID
PaymentFromID
(etc.)


and so on....