If you want to release it you just give people the 8xp of your library and they can use it in the same way.

Nice to hear. Good luck for finishing it.

If you have stored your string at the begining of the appv (with a copy for example), then you can use the pointer to the appv as a pointer to the string. Just remember that you have to store the 0 of the end of the string.
You can do for example, if the string "TOTO" + the 0 is stored in the appv TEST :
 
Getcalc("appvTEST")->P
Disp P

and it will display the string stored.
 

UPDATE


YAY!

:.FILELIB
:...
:DO NOT COMPILE AND RUN!
:BAD THINGS WILL HAPPEN
:...
:Return
:.FSM("appvStr4",SIZE)
:Lbl FSM
:!If GetCalc([r1])->Θ
:GetCalc([r1],[r2])->theta
:End
:[r1]->{Θ}^^r
:[r2]->{Θ+length([r1])+1}^^r
:Return
:.FLL(filenum,"name","size")
:Lbl FLL
:If [r1]=1
:[r2]->{Θ+30}
:[r3]->{Θ+46}
:End
:If [r1]=2
:[r2]->{Θ+61}
:[r3]->{Θ+77}
:End
:If [r1]=3
:[r2]->{Θ+92}
:[r3]->{Θ+108}
:End
:If [r1]=4
:[r2]->{Θ+123}
:[r3]->{Θ+139}
:End
:If [r1]=5
:[r2]->{Θ+154}
:[r3]->{Θ+169}
:End
:If [r1]=6
:[r2]->{Θ+185}
:[r3]->{Θ+200}
:End
:Return
:.FKL()
:Lbl FKL
:DelVar Θ
:Return
:
:Lbl FBN
:!If GetCalc([r1])->[r2]
:GetCalc([r1],768)->[r2]
:End:SortD(Θ,768)
:Copy(Θ,[r2],768)^^r
:Return
:.FCL(byteSTRT,length(bytes))
:Lbl FCL
:For([r4],0,[r2])
:[r3]->{Θ+([r1]+[r4])}
:End
:Return
:
:Lbl FAR
:Archive Θ
:Return

If anyone can help me dubug this that would be nice...Please excuse the strange syntax.

Well as I said since it's not meant to be compiled alone, it should start with two dots.

Ok so if anyone can help make sense of this that would be great!

Woah, you wrote this code and don't know what it does? And you want us to figure it out? Yikes!

It's great to have people collaborating on code, but we really can't write or debug code for you. Maybe snippets of code (3-6 lines), sure. But we can't do your whole project! (In fact, if your "snippets of code" compounds to your entire project, that's bad too!) You have to understand that everyone is busy - we'd love to help with programming questions, but you can't just dump code here and expect us to critique it.  Before asking any questions, we want to see that you've done a bare minimum research into the questions you'd like to ask, and the APIs you're asking about. If you have looked everywhere - Google, Omnimaga forums, Axe documentation, etc. - then we are more receptive to helping you out!

So my challenge to you: what's wrong with your code? How can it be made better? What don't you understand about it, and how can you fix that? Spend at least 5 hours pondering on that, without any distractions, interruptions, or delays. If within that time, you've consulted every resource available, and you've put forth your best, good faith effort into solving this, and are sweating/head-desking over the issues with your code after 5 hours of heavy research and problem solving, come back to us for questions! If you still have questions then, I promise you that the stuff you'll be asking us will be great!

Your putting words in my mouth, I wrote the code, I have now worked on this for 18 and I dont think its too much to ask for people to look at a post, see a major flaw (or even a minor one) comment on it and explain.

"if anyone can help make sense of this" is basically asking us to figure out what you wrote. That's kinda like blindly writing a letter in Arabic and asking someone to decipher it...
From my experience with coding (and pretty much everyone else's), the person who wrote the code knows it best. If you don't know what you wrote, then who else will?

This is my point, I used to scrapes of information I was given and came up with something that works but I don't know how the appvar works, and still do not. I need some more information about why i cant pull the information back out. Was it put in wrong etc.?

I'm trying to say that you didn't put enough effort. Did you read the forums? Did you read the Axe documentation? Did you test it out yourself? I know you definitely didn't do the first two because you really didn't do the last one at all! From some very little experience with Axe, the code looks really wrong to me. Compiling this would not be too pretty. Which leads me to this...

No I will not spend five hours of my day questioning what I wrote. Look at the post above yours and you will see that i cleared up the confusion about what it does.

18 hours? More like 18 seconds or something! Please, please take some time to actually learn Axe. We're not here to teach you Axe. We're here to help you learn Axe. There's a difference: teaching is to actively teach you Axe, while learning is a student and teacher thing. In essence, you must put in effort to learn Axe so that we can help you learn. It's kinda like going to school - the teacher can teach you, but you will only learn if you do your homework! (This is very true, especially in college!) If you learn it, I promise that you will come out knowing Axe much, much better than before!

We want to help you. But you must show us that you at least took some time and effort to make your code good so that we can help you better!