Transcript Phase 1: Audit Framework Audit Universe

Test
Test
test
Please press the F5 key to begin.
(Then, press the Page Up or Page Down
keys to move through the following 3
slides.)
Test
Architecture
Test
test
The network server stores the
Audit Leverage “back-end
database,” which can be in either
Access or SQL Server. It contains
the actual Audit Leverage tables
and data, but no interface.
Network Server
User Desktop
User Laptop
User Laptop
Test
Test
Audit Leverage Architecture
test
The user’s local machine contains:
Network Server
The Audit Leverage “front-end” file: the
user interface (an Access file), which
constantly “talks to” the back-end data.
…and
(for laptops only)
The Audit Leverage “local back-end”
database: a copy (“replica”) of your Audit
Leverage network database.
User Desktop
User Laptop
User Laptop
Connection Options
while traveling
Test
Test
test
Network Server
Automatic
(pre-scheduled)
synchronization
(You can also have a
separate copy of the backend database in each city.)
G:\
Master
copy of
New
York server’s
London server’s
back-end
back-end database
database
back-end database
User Laptop
User Desktop
Front-end
Synchronization
With server
Option #1
(via WAN
or VPN)
User Laptop
Front-end
Front-end
Option #3
Option #2
(c:\)
Local back-end
database
Peer-to-peer
synchronization
Local back-end
database