If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
I have another question. Sorry.
I am creating a new database in access by importing the information in our
billing office to it from excel. (I'm not an expert so Im having some concerns. Once I get all of the information imported from excel into the access database, there is still alot I have to do before I turn it over to the company like queries and forms etc. My question is. Once I import the information, how do I keep that information updated everyday until I am ready to hand it over? -- Christi Lee |
#2
|
|||
|
|||
I have another question. Sorry.
You can input the data directly to the database.
"Christi Lee" wrote: I am creating a new database in access by importing the information in our billing office to it from excel. (I'm not an expert so Im having some concerns. Once I get all of the information imported from excel into the access database, there is still alot I have to do before I turn it over to the company like queries and forms etc. My question is. Once I import the information, how do I keep that information updated everyday until I am ready to hand it over? -- Christi Lee |
#3
|
|||
|
|||
I have another question. Sorry.
Could you please tell me how? Do you mean to have everyone keep track of
their updates and give them to me at the end of the day so I can input them? -- Christi Lee "RJamis" wrote: You can input the data directly to the database. "Christi Lee" wrote: I am creating a new database in access by importing the information in our billing office to it from excel. (I'm not an expert so Im having some concerns. Once I get all of the information imported from excel into the access database, there is still alot I have to do before I turn it over to the company like queries and forms etc. My question is. Once I import the information, how do I keep that information updated everyday until I am ready to hand it over? -- Christi Lee |
#4
|
|||
|
|||
I have another question. Sorry.
While there are a lot of details (some of which only you know) to implement
this, here are a few thoughts to guide it. First if you haven't done so already, start by defining the nature and structure of the information that need to be databased. Then define tables and data definitions / rules for data in the tables. Get help from this forum if needed. The make sure everything that goes into those tables meets those rules / definitions. This includes anything that is placed into your tables via importing. Generally you want to get valid data in as soon as you can. If you have any uses of your data where you don't want to look at the newest entries, then have a field (with entry date or somehting) which lets you selectively "hide them" e.g. via a query criteria. Finally, you mentioned "there is still a lot I have to do before I turn it over to the company like queries and forms etc." Anything involving calculating/summarizing.presenting data in Access is designed once (reports, queries, forms etc.) and then should take only seconds of your time to "do." Of course, if they are placing other requirements on how you give it to them (bound in leather, hand carved in wood etc. :-) ) that will take you time, but those are off-line work and not a DB question. |
#5
|
|||
|
|||
I have another question. Sorry.
Don't know if you got what you wanted. But I was figuring if you are using
data from an excel spreadsheet which will be constantly updated, you need to link the table rather than Import it. "Fred" wrote: While there are a lot of details (some of which only you know) to implement this, here are a few thoughts to guide it. First if you haven't done so already, start by defining the nature and structure of the information that need to be databased. Then define tables and data definitions / rules for data in the tables. Get help from this forum if needed. The make sure everything that goes into those tables meets those rules / definitions. This includes anything that is placed into your tables via importing. Generally you want to get valid data in as soon as you can. If you have any uses of your data where you don't want to look at the newest entries, then have a field (with entry date or somehting) which lets you selectively "hide them" e.g. via a query criteria. Finally, you mentioned "there is still a lot I have to do before I turn it over to the company like queries and forms etc." Anything involving calculating/summarizing.presenting data in Access is designed once (reports, queries, forms etc.) and then should take only seconds of your time to "do." Of course, if they are placing other requirements on how you give it to them (bound in leather, hand carved in wood etc. :-) ) that will take you time, but those are off-line work and not a DB question. |
#6
|
|||
|
|||
I have another question. Sorry.
Thank you so much for the info, I really appreciate it. I am really new and
a lot to learn -- Christi Lee "Fred" wrote: While there are a lot of details (some of which only you know) to implement this, here are a few thoughts to guide it. First if you haven't done so already, start by defining the nature and structure of the information that need to be databased. Then define tables and data definitions / rules for data in the tables. Get help from this forum if needed. The make sure everything that goes into those tables meets those rules / definitions. This includes anything that is placed into your tables via importing. Generally you want to get valid data in as soon as you can. If you have any uses of your data where you don't want to look at the newest entries, then have a field (with entry date or somehting) which lets you selectively "hide them" e.g. via a query criteria. Finally, you mentioned "there is still a lot I have to do before I turn it over to the company like queries and forms etc." Anything involving calculating/summarizing.presenting data in Access is designed once (reports, queries, forms etc.) and then should take only seconds of your time to "do." Of course, if they are placing other requirements on how you give it to them (bound in leather, hand carved in wood etc. :-) ) that will take you time, but those are off-line work and not a DB question. |
Thread Tools | |
Display Modes | |
|
|