Ini files with flash SWF?

Hi, the INI object should work just fine with flash. Are you using ini++? That is not compatible currently.

What is actually happening when you try to use it? How are you loading the ini data / configuring it in the object's properties.

You dont need to write any patname for the ini file in SWF builds, SWF builds automatically store ini in a default folder ( you dont have a choice ).
I made a thread about this myself, but the Forum search function is so bad i cannot find it ( or maybe in just stupid ).

However ( again i cannot confirm cuz of search problems ), i remember that SWF exporter store external data files ( ini maybe? ) as .sol files in some situations, which makes it impossible to read.
I am using INIs to read and write sucessfully in a SWF app, so it is possible.

Instead of a pathname, just write the name you want the INI file to have.
Example: Pathname = "Hiscores"

An INI file with the same name wil automatically be written to:
C:\Users\<USERNAME>\AppData\Roaming\MMFApplications
If using Windows

..
I made a smple Test Application just now to confirm it:
- I made an Empty Application
- Included INI Object ( didnt mess with any properties )
- Set Pathname BANG
- Made an Event which wrote number '8' to the file
- Ran Application
- Searched for BANG.ini

And there it was, an INI file called BANG with the number 8 in it.

Don't use AppPath$+ just use

Global String A + ".ini"

Flash won't reference AppPath$.

Yes, this is correct but you don't need to worry about calling .sol, just Set Current File (Global String A+".ini") and MMF2 handles all the temporary datafile name conversions etc.

Apologies here but I'm failing to understand what the problem is

Ah, im sorry for confusing you Eagi.
What you are experiencing sounds correct and you shouldnt worry.

When you run as an actual EXE
C:\Users\<USERNAME>\AppData\Roaming\MMFApplication

When you run as an actual SWF
C:\Users\<USERNAME>\AppData\Roaming\Macromedia\Flash Player...something something something

...
If you are able to Write and Read a simple value to the INI file at this point, everythings A OK
The files might bee hidden by default, and you might need to check that somthin' somethin' under Folder Options for Windows

The .sol problem i mentioned earlier was for Arrays, MMF2 can only write to Arrays in SWF mode but not read from them.

You want both the EXE and the SWF version of your Application to save the INI files in the same location?

You can choose the loaction in the EXE version, but im pretty sure you dont have a choice in the SWF version ( INIs are saved in a fixed location which you cannont change as far as i know )

EDIT: You may be able to move the INI file to another location whenever you dont need to Read or Write to it, by using the FileObject...
But is sounds like a hazzle
Ops, scratch that, there is no File Object for SWF Applications

Hmmm, interesting idea
That sux however, i think this is a limitation with Flash however and not MMF2s fault

Long shot, but maybe this might give you some ideas
Please login to see this link.

Quote from Eagi

The thing is I need the file to be placed in a shared dropbox folder, (so that several people/computers can run the same database file while running independent SWF files on each computer) so if the ini is placed in a fixed folder on my computer then I'm in trouble since the other people wont have access to it.

Well, you can't do that with Flash. It would have to be an EXE file if you wanted it to do that.

Dredging up an old thread because i can't figure out where my ini file is being written. When i play via EXE my INI file works great. When i play via SWF, the INI file has some of my data, but not all of it! I just want to look at the file to know for sure what's going on. I don't specify a path for the ini file, as previously mentioned (above in the thread) there is no need to provide a path, so i don't.. I just give it a name. can't find the file anywhere.

thanks and Merry Christmas and Happy Holidays

Edit: Nevermind, i found the location (as posted above its in the #localWithNet folder...

Now i can see that i should be using groups as this should make it easier... so i'll test it with groups and try again.