[AccessD] Video Rental DB

[David McAfee]

This just made my head hurt :D

Tax inspectors? Courts? :O
On Jul 1, 2016 1:55 PM, "James Button" <jamesbutton at blueyonder.co.uk> wrote:

> Swift assessment of the needs  - guesswork -
> Stock item - code, title, media type, Discs in set , booklet, loan
> limitations -
> as in content type,  current reported condition, date purchased, source,
> Brand,
> cost, depreciation anticipated each year, depreciation to-date, date
> written-off
> from stock
> Customer - Account,  name, address, phone - home mobile, email, payment
> method
> and payment account - bank account (reference - and confirmation of id
> address),
> id validation presented - type and reference - social services -
> government id,
> guarantor, registered date, last borrowing date, number of borrowings  -
> problems level marker - scuffed, returned as damaged, damage admitted at
> return,
> Damage found at return, incomplete at return, payment problems - etc...
> and a
> freeform text comment area 2000 characters (warning to staff on the form
> about
> libellous entries and the possibility of them being required to justify
> their
> entries at court.)
>
> Borrowing entry - Customer account, date,  Invoice number, Billed amount,
> Excess
> charge, Paid amount , closed entry - all returned, or excess paid
> Invoice entry line - invoice number, stock code,  date out, expected loan
> duration, returned OK marker
> If not returned OK - then there will be a 'line-item problem report'
> As in customer, invoice, stock code, excess charge, Problem customer
> grading,
> and commentary entry
>
> So you can monitor the profitability of each item you bought - and maybe
> still
> have.
> You can monitor customers for frequent damage, complaints
> You can monitor customer business - at a gross level, and using invoices
> at a
> very specific level
> You can easily generate summary reports of the business's processing during
> whatever period you consider appropriate.
>
>
> So - considerations
> Security and backup -  practical day-by-day, to put on a new system when
> the
> store gets robbed, Auditors, tax inspectors, and courts
> Access recording - I haven't included anything to do with who made the
> entries -
> that would imply individual access and logons - maybe bar-code card or
> proximity
> tag/card readers - and that would imply a log of every action made in the
> database.
> Going to use views and access permissions by user
> Going to use imbedded VBA to validate and process form entry onto the data
> tables
> Back-end and multiple front-end PC's (tablets?) encryption for  connections
> between the back end and front-end devices - Access run-time?
> What will you be using as a database management facility when you have
> finished
> the prototyping and development
> And - backup and recovery to address corruption of the database - Ah! Yes
> wireless input ! - maybe create flat file input sets to be passed from the
> input
> form presentation  devices back to the data store - so all updates are
> done as
> processing input transaction set files.
>
> JimB
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>