At 06:49 PM 12/20/99 -0500, you wrote: >Is there a easier way to do this other than by creating a >database record or is that the way to go? I would imagine you could find >the location in memory of that int, lock it down and change it, from the app >itself? or not? Er, creating a database record _is_ finding a location in memory and locking it down etc. This is the way to go - just make a database with the same creator as your app & type 'DATA' or whatever and put whatever you like in it - when your 'appl' is deleted, the other DB should go with it.
- Persistant data storage for registration purposes? Rubin, Dan
- Re: Persistant data storage for registration purpo... Brian Mathis
- Re: Persistant data storage for registration purpo... Charles Rezsonya
- RE: Persistant data storage for registration purpo... Rubin, Dan
- Re: Persistant data storage for registration purpo... Tim Hewitt
- RE: Persistant data storage for registration purpo... Michael S. Davis
- RE: Persistant data storage for registration purpo... Rubin, Dan
- Re: Persistant data storage for registration purpo... Jason Dawes
- Re: Persistant data storage for registration purpo... Ben Darnell
- RE: Persistant data storage for registration purpo... Roger Chaplin
- Re: Persistant data storage for registration purpo... Jason Dawes
- Re: Persistant data storage for registration purpo... Ben Darnell
- RE: Persistant data storage for registration purpo... Ronald Gouldner Jr
- Re: Persistant data storage for registration purpo... Daniel Rubin
- Re: Persistant data storage for registration purpo... Aaron Ardiri
- RE: Persistant data storage for registration purpo... Joseph Showalter
- RE: Persistant data storage for registration purpo... Aaron Ardiri
- RE: Persistant data storage for registration purpo... Miller, Gary
