A Microsoft Office (Excel, Word) forum. OfficeFrustration

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.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Update Tables



 
 
Thread Tools Display Modes
  #1  
Old August 2nd, 2007, 10:16 AM posted to microsoft.public.access.tablesdbdesign
SGTPEP
external usenet poster
 
Posts: 33
Default Update Tables

Currently i import 2 excel files into my database, at different times.

I am looking to update one of the tables depending on the information on the
other. i.e. The first table is stock gained and the second table is the stock
sold.

I wold therefore want to be able to update the stock table to say that the
item has been sold.


Beginner
  #2  
Old August 2nd, 2007, 04:10 PM posted to microsoft.public.access.tablesdbdesign
Jeff Boyce
external usenet poster
 
Posts: 8,621
Default Update Tables

It sounds like you are using the imported Excel data directly, rather than
using queries to parse the (raw) import data into more permanent
(?well-normalized?) Access tables. If this is your situation, you will not
get as many benefits from Access' relationally-oriented features/functions.

For instance, in Access, you could consider using a SINGLE table
(transactions), into which both sold and received stock units could be
recorded.

Then you'd only need to sum up the transactions for StockItem=93 to see
stock-on-hand.

Or maybe I'm not following your situation well...

Regards

Jeff Boyce
Microsoft Office/Access MVP

"SGTPEP" wrote in message
...
Currently i import 2 excel files into my database, at different times.

I am looking to update one of the tables depending on the information on
the
other. i.e. The first table is stock gained and the second table is the
stock
sold.

I wold therefore want to be able to update the stock table to say that the
item has been sold.


Beginner



  #3  
Old August 2nd, 2007, 04:34 PM posted to microsoft.public.access.tablesdbdesign
SGTPEP
external usenet poster
 
Posts: 33
Default Update Tables

Hi,

I have resolved the problem using querys, thanks.

The reason for not using one table is that a employee may list the stock but
it may not get sold for months, therefore the listing and the sale could be
months apart, and therefore not on the same monthly report!

We operate like a franchise system so i dont actually do any buying or
selling, i collect the royalties from the 'employees'



"Jeff Boyce" wrote:

It sounds like you are using the imported Excel data directly, rather than
using queries to parse the (raw) import data into more permanent
(?well-normalized?) Access tables. If this is your situation, you will not
get as many benefits from Access' relationally-oriented features/functions.

For instance, in Access, you could consider using a SINGLE table
(transactions), into which both sold and received stock units could be
recorded.

Then you'd only need to sum up the transactions for StockItem=93 to see
stock-on-hand.

Or maybe I'm not following your situation well...

Regards

Jeff Boyce
Microsoft Office/Access MVP

"SGTPEP" wrote in message
...
Currently i import 2 excel files into my database, at different times.

I am looking to update one of the tables depending on the information on
the
other. i.e. The first table is stock gained and the second table is the
stock
sold.

I wold therefore want to be able to update the stock table to say that the
item has been sold.


Beginner




  #4  
Old August 2nd, 2007, 05:20 PM posted to microsoft.public.access.tablesdbdesign
Jeff Boyce
external usenet poster
 
Posts: 8,621
Default Update Tables

Whether or not a specific stock item showed up in one month or another, a
single transaction table would receive the updates from BOTH Excel feeds,
each month. That single transaction table would provide a cumulative
history, rather than having to search multiple "months" data.

Regards

Jeff Boyce
Microsoft Office/Access MVP

"SGTPEP" wrote in message
...
Hi,

I have resolved the problem using querys, thanks.

The reason for not using one table is that a employee may list the stock
but
it may not get sold for months, therefore the listing and the sale could
be
months apart, and therefore not on the same monthly report!

We operate like a franchise system so i dont actually do any buying or
selling, i collect the royalties from the 'employees'



"Jeff Boyce" wrote:

It sounds like you are using the imported Excel data directly, rather
than
using queries to parse the (raw) import data into more permanent
(?well-normalized?) Access tables. If this is your situation, you will
not
get as many benefits from Access' relationally-oriented
features/functions.

For instance, in Access, you could consider using a SINGLE table
(transactions), into which both sold and received stock units could be
recorded.

Then you'd only need to sum up the transactions for StockItem=93 to see
stock-on-hand.

Or maybe I'm not following your situation well...

Regards

Jeff Boyce
Microsoft Office/Access MVP

"SGTPEP" wrote in message
...
Currently i import 2 excel files into my database, at different times.

I am looking to update one of the tables depending on the information
on
the
other. i.e. The first table is stock gained and the second table is the
stock
sold.

I wold therefore want to be able to update the stock table to say that
the
item has been sold.


Beginner






 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 07:49 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.