Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Memo Field 1
- Thread starter directorz
- Start date
-
1
- #3
...but be wary of the limits of a memo field.
A memo field is not like most other data types in Access (text, numeric, date). It is more like an object where Access uses a pointer to point to the memo.
Only the first 255 characters of a memo field (Access 2000 and above) can be searched, etc.
Designing code to emmulate a "combo box" would be very tough.
A memo field is not like most other data types in Access (text, numeric, date). It is more like an object where Access uses a pointer to point to the memo.
Only the first 255 characters of a memo field (Access 2000 and above) can be searched, etc.
Designing code to emmulate a "combo box" would be very tough.
- Thread starter
- #4
Well, I'm not really trying to emulate a combo box. Let me elaborate.
In a vehicle maintenance db, I need to provide an item checksheet for vehicles that are routinely inspected at pre-determined intervals. The checksheet, which is a memo field, includes things like check lites, check battery etc. The checksheet is simply a printable form to be used as a reference by a mechanic as he / she checks a vehicle. The field, once established with a check sheet will not be used as a data entry form with individual entries.Because each vehicle and interval are different, the checksheets will vary. I may end up with 5 of these 'templates' to be used among 50 vehicles.
In one table, I want to store the PM name (preventive maintenance), the interval (say 7 days) and the associated checksheet. This table will serve as a lookup table. A second table stores a vehicle number and info about it's assigned PM's, looking up this info from the first table. So, my layout is something like this:
Tbl1:
PMNAME - PK
PMINTERVAL - PK
CHECKLIST
Tbl2:
UNIT ID - PK
PMNAME - PK
PMINTERVAL - PK
CHECKLIST
The goal is to keep these check sheets, which are 'templates' in Tbl1 and, as new vehicles are entered into the system in Tbl2, a user can 'lookup' the checksheet he wants to use from Tbl1 and associate it with a vehicle, then store it in Tbl2...whew. Basically, the classic scenario but I have the memo field problem. Are there any workarounds?
Thank you
In a vehicle maintenance db, I need to provide an item checksheet for vehicles that are routinely inspected at pre-determined intervals. The checksheet, which is a memo field, includes things like check lites, check battery etc. The checksheet is simply a printable form to be used as a reference by a mechanic as he / she checks a vehicle. The field, once established with a check sheet will not be used as a data entry form with individual entries.Because each vehicle and interval are different, the checksheets will vary. I may end up with 5 of these 'templates' to be used among 50 vehicles.
In one table, I want to store the PM name (preventive maintenance), the interval (say 7 days) and the associated checksheet. This table will serve as a lookup table. A second table stores a vehicle number and info about it's assigned PM's, looking up this info from the first table. So, my layout is something like this:
Tbl1:
PMNAME - PK
PMINTERVAL - PK
CHECKLIST
Tbl2:
UNIT ID - PK
PMNAME - PK
PMINTERVAL - PK
CHECKLIST
The goal is to keep these check sheets, which are 'templates' in Tbl1 and, as new vehicles are entered into the system in Tbl2, a user can 'lookup' the checksheet he wants to use from Tbl1 and associate it with a vehicle, then store it in Tbl2...whew. Basically, the classic scenario but I have the memo field problem. Are there any workarounds?
Thank you
directorz
I think I understand.
Question are you interested in storing the results of each form that has been checked??
If so, then a memo field is probably not the best way to approach the problem. I previously posted a "check list" design elsewhere - see May 20th posting by myself, and May 26th by DanJR in the following link...
As indicated by Dan, the design is very flexible.
If not, you might want to think outside the box and store your PM stuff in the Access database and link to the template which is stored externally to Access as a DOC (Word) or PDF (Acrobat) file. A WordProcessor may be a much better tool to design templates.
Richard
I think I understand.
Question are you interested in storing the results of each form that has been checked??
If so, then a memo field is probably not the best way to approach the problem. I previously posted a "check list" design elsewhere - see May 20th posting by myself, and May 26th by DanJR in the following link...
As indicated by Dan, the design is very flexible.
If not, you might want to think outside the box and store your PM stuff in the Access database and link to the template which is stored externally to Access as a DOC (Word) or PDF (Acrobat) file. A WordProcessor may be a much better tool to design templates.
Richard
- Thread starter
- #6
I will try to clarify more. "...store the results..." The results of the checksheet will be stored but not here in the memo field. The memo field will only be used to create a checksheet form which can be printed. That's it, nothing more. The only data in the memo field is the form itself which is created by the user. No data is stored here. Now, let's say that a mechanic runs a check on a vehicle based on the items that are on the checksheet. Yes, in ANOTHER area of my db, he / she then records the results, noting if any probs were found etc.
...sample
( ) check oil
( ) check battery
( ) check lites
...and so on. The user prints this form then physically writes in results with a pencil. This is a printable form only
...sample
( ) check oil
( ) check battery
( ) check lites
...and so on. The user prints this form then physically writes in results with a pencil. This is a printable form only
- Thread starter
- #7
directorz
There are two drawbacks as I see it...
- The document may be moved from the directory / folder location on the server or desktop.
- An unauthorized person may edit the document.
Both of these are "manageable" via security settings on the directory if the documents are stored on a server. If the documents are stored on a local PC, then control would be done by the local owner of the PC.
Richard
There are two drawbacks as I see it...
- The document may be moved from the directory / folder location on the server or desktop.
- An unauthorized person may edit the document.
Both of these are "manageable" via security settings on the directory if the documents are stored on a server. If the documents are stored on a local PC, then control would be done by the local owner of the PC.
Richard
- Thread starter
- #9
- Status
