Display text configuration files via option group

cdcox

Registered User.
Local time
Today, 00:48
Joined
Aug 29, 2005
Messages
21
Hopefully this will be something new that someone will be willing to try since I haven't been able to find anything like this in the forum....

We have 7 pieces of equipment (routers/switches/encryptors) that all have large text file configuration data. What we want to do, if possible, is to create an option group and a memo block, so that when we click any one of the pieces of equipment in the option group, the text configuration file will display in the memo block and we will be able to save it as part of the record. Is this even possible or is there a better solution?

This would be the equivalent of simply using a command button to launch notepad with the configuration data.

Your help would be greatly appreciated!!!!
 
create a text box and use the Dlookup function to populate it with the Memo data using the option group to give the value to the where clause

HTH

Peter
 
I am attaching a screen shot of what it is we're looking at. Like I said, I'm a newbie so I don't really understand what you are saying. Look down to the lower right of the form. When I click on cisco 1751, I want to see the text configuration file for the 1751 in the memo block below it. Same goes for the 2651 and every other piece of equipment below it. Thanks.
 

Attachments

You can import the config file into a memo field in the device record.
 
The only import option I can find is done at the form level. When you initially create the option group, it asks you what labels you want and what values you want stored into those labels (the defaults are integer values based on the number of labels in the option group). Then it asks you what field you want to store the value in, in which case I selected the memo box I created. It DOES work with the integer values, but the problem is, I can't edit those values and save them--it just goes right back to storing the individual integer values in the memo box. I can't find any option that will allow me to import a text file into the memo block.
 
Import was probably a poor choice of term. You would need to copy and paste into the memo field.
 
Here is a small demo db of what I meant. You would not save the text itself but the reference to it in the lookup table. If you need to be able to relate more than one of the texts to a single record then you will need to use a join table to store the data.

HTH

Peter
 

Attachments

Peter--
You are THE man! That is exactly what we're looking for and unfortunately, the coding/commanding that was involved is a bit above me. The problem we were having is that when you create the option group, you can assign a value to the labels and that is the ONLY value that you can store in the memo block--you can't save it, and that was the real struggle! So, perhaps you can assist us with our "ping" problem as well? You seem to understand just what it is we're looking for. Thanks.

http://www.access-programmers.co.uk/forums/showthread.php?t=93258
 
Peter--
While this did work in your example, I am unable to get it working in my own form. I keep getting the error "Control can't be edited; it's bound to the expression '=DLookUp("[HsdnSiteInfo]","[tblHsdnSiteInfo]","partID = " & [optText]).' What am I missing here? I went online to look up information on the dlookup function and I am actually confused by the 1st and 3rd fields in that command. I am not sure from what the expression is derived from, and what the "partID=" & [optText])' is doing. I understand that the optText is actually the option group. I just can't seem to get rid of that error. And should I be using a text box or a memo box?
 
The sample I sent you does not save the data it only looks it up.
I assumed that you had three standard references that you wanted to be able to view at the click of the option group.

If these are standard texts and you want to associate just one with each record, then you would not normaly store the text but the reference to it. You could do this by joining a lookup table, with the text data, into the underlying query of the form.

if you have more than one unique text to store per record then you are going to need another method.

Peter
 

Users who are viewing this thread

Back
Top Bottom