Persistent data in unbound textboxes

vanceric

New member
Local time
Today, 03:54
Joined
Mar 25, 2014
Messages
7
Hello everyone. I have a little issue and I'm not sure what the best approach is to fix it. I've built a rather robust database that needs to be idiot proof. Chances are after I leave there will be little to no back-end maintenance on it. There are hyperlinks throughout the database as well as a few lines of code that reference network locations that could change 1-2 years down the line. What I need to do is build a "housekeeping" form that is password protected where users can edit those hyperlinks via text-boxes. My problem is I'm not sure where to store the the data from the text-boxes to make it persistent. Making a table for the hyperlinks seems to be the wrong approach but I could be wrong.

Example:
Form1-Button1="String1"
String1="HousekeepingForm-TextBox1"
HousekeepingForm-TextBox1="X:\Stuff"
 
I don't understand why you object to using a table. However an alternative is to store them as database properties.
 
I don't understand why you object to using a table. However an alternative is to store them as database properties.
Thanks for the reply... my issue with a table is that I would only need 1 record to accomplish the task and if the form for input got switched to record number 2 they may not be able to get it back to 1. I know I can disable navigation but it still scares me.

Could you elaborate a little more on using database properties?
 
Exactly what I needed. Simple and it works.
For anyone interested in the end result
Function link1Update() 'Updates the property
Dim DB As Database
Dim P As Property
Set DB = DBEngine(0)(0)
Set P = DB.CreateProperty("Link 1", DB_TEXT, [Link 1 Textbox])
DB.Properties![Link 1] = P 'This is only for update, to make the initial property this line should be: ("DB.Properties.Append P")
End Function

Function linkOne() 'Grabs the property you just saved
Dim DB As Database
Set DB = DBEngine(0)(0)
CopyRight = DB.Properties![Link 1]
End Function

Private Sub updateLink1() 'Button to follow hyperlink
Application.FollowHyperlink linkOne()
End Sub
 
I have a Menu Form and put all the Constants hidden on the Form. Amongst the Control are fields that point to the the web site and help system. So if you have have to switch which happens you can simply have a button to toggle between records. The information is held in a table. In my case I have multiple front-ends for each company.

Simon
 
I have a Menu Form and put all the Constants hidden on the Form. Amongst the Control are fields that point to the the web site and help system. So if you have have to switch which happens you can simply have a button to toggle between records. The information is held in a table. In my case I have multiple front-ends for each company.

Simon

Unfortunately I think that wouldn't really work in my instance as well as using a DB Property. For instance if my end user changes the file path where they export data from "X:\Stuff\" to "Y:\Stuff\" I need a simple form where they can just go change the directory that an export button points to. Another instance would be my customer uses "www_thingsandstuff" to research now but in 2 years they want to use "www_stuffandthings" all they have to do is change the text-box on their "maintenance" form to the proper URL and then click the button to set that DB property to what they typed.
 
I think that whilst building flexibility if you instance the directory changes to Y:\Stuff\ want happens to the information in X:\Stuff\. The only way the information can be retreived is all the information is in the same place unless you store the path of all the relevant records.

It is the just the same changing a table from www.thingsandstuff to www.stuffandthings.

I will give you another example is an Artist is invited to a Group Show so several images maybe provided so these images are stored \Originals\Misc\ however if the Artist becomes a house Artist then a directory will be created for that Artist because there will now be numerous images. The images in Misc have to be moved to the Artist specific Directory. With 20,000 images I not going to store the Image Path on every record just the Artist.

Simon
 

Users who are viewing this thread

Back
Top Bottom