Challan and Deductee Worksheets - Creating New Tables Every Quarte

[Guest]

I have two seperate worksheet formats in which I have to fill data every
quarter, containing information about the tax deducted at source from a set
of suppliers to whom we are making payments more than one times in a month.
Basically, I have the information fed into these sheets on a quarterly basis
by my staff, but the problem is that with frequent software changes, which do
not affect the basic structure of the data contained in these sheets, but
does affect the way in which this data is to be presented for electronic
submission to the Department of Income-Tax, I have tentatively decided to
create my own software for dealing with the same, so that whatever changes
take place can be dealt with at my level from time to time. The problem that
faces me today is the basic format of the data in which I want to import
these worksheets into, because of the fact that at the end of every four
quarters, I have to retrieve this data for the issuance of Tax Certificates
to the said suppliers, for various purposes, which I shall not detail at this
moment. I am seriously considering importing the excel sheets into an Access
Database for every concern whose work that I take up on an assignment basis,
but the problem is that there cannot be just one database for all the
concerns, I must have the flexibility of creating a new database for every
concern whose work thatI take up.

What I need some help is in creating a new database and the tables the first
time that I access the excel worksheets, does someone already have some
programs which I can modify for my specific use, since I am short of time,
and do not have the time to actually sit and write out all the relevant code
in the space of just two weeks, by which the first deadline for the
production of this data falls due.

Please help, if you need any more information regarding this issue, please
send me a message and I shall respond immediately through this forum.

Thanks,

 

[Guest]

You will likely not be able to get it done in two weeks. As to a separate
database for each concern, that is not the correct way to do it. You should
have a field in one of the tables in your that identifies the concern. You
then use filtering to show only the concern you want to work with.

 

[Guest]

The thought did occur to me, but since the particular organisation might want
their data exclusively in one database, for their internal storage of
quarterly and annual data, it might not be the best idea to keep all the
information in one database. Either I seperate the databases or I have some
way of identifying the tables with each concern, is what I would plan to do.

 

[John W. Vinson]

The thought did occur to me, but since the particular organisation might want
their data exclusively in one database, for their internal storage of
quarterly and annual data, it might not be the best idea to keep all the
information in one database. Either I seperate the databases or I have some
way of identifying the tables with each concern, is what I would plan to do.

As Dave says: storing data in a database name is bad design. Storing data in a
tablename is equally bad design.

If you need to separate the data from different organizations, *a query will
do that for you* if you have the OrganizationID as an indexed field in the
table.

John W. Vinson [MVP]