🚀 go-pugleaf

1) Allocating Stock
Use an "Allocated Stock" column in the stock table to manage count of stock
that is allocated to jobs/people. Adjust physical stock levels when the
allocation is finally given or cancelled. Show reps the "Available Stock"
number (physical-allocated). Allocate at your earliest chance. (An allocated
stock item could take days to be removed from stock if the customer intends
to collect later for example).

2) Deleting Stock Transactions
You are unlikely to want to delete stock transactions until year-end. Just
mark the employee as deleted. Stock movement analysis will require all stock
transactions to be available.

3) Using while backing up.
Depends on the database. Some may allow you to do it. For month-end and
year-end it is recommended no one is connected so you have clear cut off
points.

4) If a relation is defined and the relation fields contain values then most
databases will prevent you from having failed links. Try and keep your
design simple and let the database do what it naturally does.

5) If you use ADO and no proprietary server code you will find it easier to
move your application to a different database.

Sorry, I can't elaborate any further on any of the points here. Good Luck!

--
Michael Collier
--

"Steve Kothenbeutel" <skothenbeutel@consultant.com> wrote in message
news:3d09fdce_2@dnews...
> Let me first identify the situation...
>
> I am designing a client/server application using the three-tier model.
The
> project is to yield a store transaction management system.  The idea is
that
> upwards of 8 workstations will be placed at various locations within the
> store all connected directly into the middleware server.  The workstations
> will be operated by various sales people.
>
> Here are my questions...
>
> (1) several customers come into the store to purchase the same item
> unknowing of each other's desire for the same product.  They all go to
> seperate salespeople and each salesperson brings the inventory up.  Each
> customer then decides to purchase the same item  The salesperson realizes
> there is only one left.  So, he sets up the transaction.  However, the
other
> sales personnel are doing the same thing.  So, here is my question... how
do
> I commit the product to a sales person while he fills out pertinent
> information about the customer?  How do I ensure that the item will be
there
> once all information is filled out and stored in the server?  If I use
> transactions for this, how would I implement this measure?
>
> (2) lets say that I have 5 salespeople employed by this store.  One sales
> person is fired.  Within the database, there is a record of all sales
> completed by that employee.  In creating the database, should I invoke a
> relationship between the employee's id in a seperate employee's table with
> that of the transaction?  Or should I just store the identity of the
> employee in the transaction without any relationship established between
the
> two tables?  If I decide to delete the salesperson from the database and
if
> a relationship exists between the two tables, wouldnt that also force a
> delete of all sales made by the employee?  And if it doesnt force the
> deletion of transactions, then would the salesperson's ID field within the
> table be left empty?
>
> (3) When packing is necessary, should I take the middleware server offline
> or can I execute a pack procedure while sales personnel have access to the
> database?
>
> (4) Lets say that I have data on my sales personnel in the same database
> file as all transactions and related information.  Is there a way to lock
> tables in the database from being deleted while I execute mass deletion
> routines?
>
> (5) If I choose to use Interbase/Firebird server, should I use a specific
> set of database components?  Are there any advantages to using dbExpress
> over ADO?
>
>
> Well, I hope I havent been too cryptic.  I am theorizing how I should
> proceed with a project I have been working on.  I appreciate any and all
> insight... THANKS!
>
>
> Steve Kothenbeutel
> skothenbeutel@consultant.com
>
>
>