A
Al
I hope I am posting this question in the right area. I'm
trying to come up with the best possible design for a
database I'm developing in Access 2000. I also have VB6
to work with.
I'm building a database for dispatchers and security
officers. I am at the point where they have requested a
way for the officers to enter an incident report for a
specific record that was logged by the dispatcher. They
want it to have spellcheck capability as well.
Here are some of the options I've been considering:
Access Memo field - My concern is can it spellcheck, and
will multiple reports daily prematurely grow the database
beyond the Access limitations.
API call to MS Word - I will have approx. 50 users and
have concerns about software versions and upgrades in the
future causing coding conflicts. I would like to store
the report's filepath in the database to minimize db
growth.
VB RichTextBox control - to build-in a static feature for
the database. This is actually the most attractive but
probably the most ambitious approach. I don't know if my
VB skills are up to the challenge.
Any suggestions to help me this design this feature will
be greatly appreciated.
TIA,
Al
trying to come up with the best possible design for a
database I'm developing in Access 2000. I also have VB6
to work with.
I'm building a database for dispatchers and security
officers. I am at the point where they have requested a
way for the officers to enter an incident report for a
specific record that was logged by the dispatcher. They
want it to have spellcheck capability as well.
Here are some of the options I've been considering:
Access Memo field - My concern is can it spellcheck, and
will multiple reports daily prematurely grow the database
beyond the Access limitations.
API call to MS Word - I will have approx. 50 users and
have concerns about software versions and upgrades in the
future causing coding conflicts. I would like to store
the report's filepath in the database to minimize db
growth.
VB RichTextBox control - to build-in a static feature for
the database. This is actually the most attractive but
probably the most ambitious approach. I don't know if my
VB skills are up to the challenge.
Any suggestions to help me this design this feature will
be greatly appreciated.
TIA,
Al