General discussion

any ideas?

I need some guidance!

We are planning on undertaking an Access project for our organization and are interested on what people think the best route to go is.

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

Discussion is locked

Follow
Reply to: any ideas?
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: any ideas?
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Comments
- Collapse -
Why Access?

A good report tool, but I've seen it buckle too many times under load and user gaffes (security issues).

Is there any chance of a MySQL database which you can secure, then use Access or VB as the front end?

Another common failing is getting a design spec in writing.

Bob

- Collapse -
hmmm

true! i'll look more into that solution. there isnt going to be real heavy usage, 3-7 users max. there might be a hold up securing the sql server, we have some restraints getting funds, tools, etc. Everyone involved has Access, that being our reason for going with it.

- Collapse -
Re: hmm

Blueboxed,

I agree with Bob.

Everybody has a browser, and ActiveX and Java (if you install it). And there are many, many tools available to write web-based applications nowadays, including links to databases of course.
And possibly your organisation has Exchange Server (and a lot more can be done with it than simply using it as a storage area for emails) or Sharepoint Server. That might be useful tools also.

So the availability of MS Access doesn't seem to be the deciding argument for the tool selection you made.


Kees

- Collapse -
Just FYI.... MySQL is not a dollar item.

It's free for you to use. I'm making great strides in stable "factory floor" applications with VB with MySQL on some machine in the brew.

Mysqlcc lets you look around and administer, and with the ODBC connections you can use Access, Excel, VB, .NET and more to work the database and make reports, etc.

Cost is not an issue with MySQL.

Bob

- Collapse -
Good idea, but inappropriate method

It's fine idea to automate gathering personal information in your organization, but method you choose is inappropriate because of following reasons:

1. MS-Acces database is really unsafe and unuseful for that goals - it's better to use MySQL, MS-SQL Server or other system, which have more powerful security and designed for network purposes;

2. Printing template -> Signing -> Scanning -> Recognizing -> Saving to DB... If you choose method you described, these steps have to be done in different applications. It's very unuseful!

Most reliable way is to develope special application for this purpose. It may be based on MS Office technology, or be independent product. Or, maybe you try to find ready solutions?

CNET Forums

Forum Info