Check out this article on DOUG: http://www.director-online.com/accessArticle2.cfm?id=442
It will give you a completely different approach - using "Data cast members" Basic idea - use a Director cast as a mini-database. When a new user logs in, create a data cast member for that user. When they exit, write their "status" into their database member. Save the castlib. Then, when a user logs in, check to see if they have been there before, if so, pull out their information from their corresponding data cast member, set up the world, and you're off and running. Good luck, Irv At 6:53 PM -0500 12/18/01, Joe Gallagher wrote: >Hello List. I've literally been researching solutions for hours, and now >turn to you... > >I'll try to make this brief, but detailed (is there such a thing? :) > >I am using Director 8.5 for windows, and am finishing up an app that will be >distributed via cd-rom (no web/shockwave). The final step is adding the >bookmarking controls. > >This course is made up of 13 small lesson loops. The user can go in any >order he/she pleases, and may exit from the main menu only. > >I have variables in place that track which lessons the user has completed. >I want the user to be able to log back in using the same ID and be able to >continue where he/she left off. A quick and dirty "flow chart" follows: > >BEGINNING THE APPLICATION >1. Start the Application >2. Enter User ID >3. When he/she clicks OK, the app will search an ini or txt file to see if >he/she has logged in on this machine before. >4. If not he/she will proceed as a first-time user. >5. If they have, a message appears asking if they want to return where they >left off. >6. If they choose to return where they left off, it will take them to the >main menu, and there will be checkmarks by the lessons that they have >already completed. >7. As the user continues through the course the variables will be updated as >the user completes the lessons. > > >EXITING THE APPLICATION >1. When the user exits again, it will write out the information (variables) >to the ini or txt file stating which lessons were completed. That way the >user can re-enter the applicaiton and continue with the course. > >NOTE: If a return user goes through the coures and chooses to start from >the beginning, then they will never be able to go to their previous >settings; they will shake the etch-e-sketch, and start over. > >I spent all afternoon reading Macromedia tech notes, archives etc, and I >still can't find a way to make this happen. Maybe the info was there, but I >just couldn't read between the lines. I can't figure out how to write out >the files in a format that will allow me to then read the information for >this specific purpose. Most of the archive messages just talk about writing >and appending for single variable instances, but I need for this to keep >track of multiple variables from multiple users. I have been using the >fileIO Xtra, but just haven't had any luck. > >Any suggesstions/samples would be very VERY much appreciciated. > >Thanks, >Joey > > >[To remove yourself from this list, or to change to digest mode, go to >http://www.penworks.com/lingo-l.cgi To post messages to the list, >email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]) >Lingo-L is for learning and helping with programming Lingo. Thanks!] -- Lingo / Director / Shockwave development for all occasions. (Home-made Lingo cooked up fresh every day just for you.) [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]) Lingo-L is for learning and helping with programming Lingo. Thanks!]
