Access Databse

[blueboxed]

ok we are thinking about designing this database, what do you guys think would be the best way to do this?

I need some guidance!

The database is stored on network drive where all persons involved in the process will have access.

The package is started:

The person’s personal information and specifics for package is entered into an Access table via form.
|
Access Report is generated (templated document where the above entered information is entered in the document)
|
Report is printed and physically signed
|
The above signed document along with the other supporting documents are scanned and placed on the network drive under the individual’s subdirectory
|
Now the package is complete and ready for review. Scanned files linked to Access automatically? Via VB perhaps?
|
Reviewing authority inputs specifics for authorizing endorsement (Access report)
|
The above, generated final endorsement is forwarded electronically (pdf?)
|
Authorizing Official electronically signs forwarded endorsement and fwds package back to originator

[Michaelw]

You are a little vague. What are you asking? Table structure? Should you use a database? ???

[blueboxed]

sorry..

i just am thinking of where to start with all of this...

what would you sugest for the digital signature?

[Michaelw]

There was an article today that SHA-1 code has been cracked. I'll admit cryptography is not one of my strengths , but RSA with sufficiently large keys is still safe, as is 3-DES, according to people that know.

I would start by defining what information you need to store and work through normalization rules at least to BC3.

Be sure and use surrogate keys and if you plan on replicating from different instances of the same database structure I would look into using guids as keys.