Failed to Save Documents

[russnobbs]

While moving some A5V7 applications to V10.5 I'm plagued by this error.

Closing the current application and opening another from a button works fine in V7. In V10 something does not like the path of the app I'm opening. I've browsed to addresses like g:\database\data\myapp.adb or used UNC style addresses. neither work.

I found a number of threads about "Failed to Save Documents" but none seem to bear on my particular problem.

[Clunes]

Re: Failed to Save Documents

I have found this error to be simply based on the path to the main adb. How do you open the db.

If it is via a shortcut then there may be an error in the a path. It can be as simple as needing quotation marks and there are spaces in the path.

Check drive mapping. Your example shows no spaces and should work, also check the user has read/write to it

Also have you tried to open the DB by using file open from the Alpha menu

[Tom Henkel]

Re: Failed to Save Documents

Russ,

Are all of your databases in the same "root" path? ie: "G:\somefolder\someapp.dbf"?

if so, then you may want to set a global variable or even an addin variable to set the "G" path and then use the variable to determine where you are and where you are going.

We have many databases that we call from a main "calling" database, and in the main calling database, we set the pathing using variables, so that we don't trip over ourselves. We've set up functions to "call" the other apps, so that we have some consistency.

Here are 2 functions we use to open an app from our main app.

'FUNCTION "SETUP" INITIALIZES THE VARIABLES TO BE SENT TO THE CALLED APPLICATION.
'	THE CHARACTER PARAMETER "appname" IS THE NAME OF THE CALLED APPLICATION AND IS WHAT IS
'		PLACED INTO THE AA.BCBSS.WHERETO SUPER-GLOBAL VARIABLE  
'		THE CHARACTER VARIABLE "FORMNAME" IS THE NAME OF THE FORM IN SOCIAL SERVICES 
'		THAT CALLED THE NEW APP.  IT IS USED TO DETERMINE WHICH FORM TO OPEN UPON RETURN
'		THE VARIABLE "RETN" IS USED TO TOGGLE THE "RETURN" MENU ITEM ON/OFF
FUNCTION setup AS V (appname AS C, formname as C )
	dim aa as p
	aa= addin.variables()
	dim aa.bcbss as P
	dim Global Retn as C
	Retn = "X"
	aa.bcbss.wherefrom = formname
	aa.bcbss.whereto = appname
END FUNCTION

FUNCTION callsub AS C (subapp AS C,path=" ")
'Function callsub is used to determine whether to use the shadowed database when calling 
'a sub application or to use the main database
'  parameter subapp has the format of "folder\appname"  leave off the ".adb" I will insert it.
'									ie:      supply\stockroom
'	parameter path is to tell where we are going to go.  "P" in path means to use "personnel" path
'		 - aa.bcbss.ppath instead of aa.bcbss.path
dim aa as P
aa = addin.variables()
dim aa.bcbss as P
dim aa.bcbss.appname[10] as C
dim aa.bcbss.applvl as N
dim aa.bcbss.subapp as C
'Set up name of Calling Application
dim aa.bcbss.calling as C
dim shared filename as C
dim filename1 as C
dim path as C
dim global mpath as C
'
aa.bcbss.calling = a5.Get_Name()
filename1 = aa.bcbss.lpath+chr(92)+subapp+".adb"
if file_exists(filename1)
	filename = filename1
end if
aa.bcbss.subapp= filename
dim good as N
good = 0
good = aa.bcbss.appname.find(aa.bcbss.calling)
if good =0
	aa.bcbss.appname[aa.bcbss.applvl] = aa.bcbss.calling
end if
aa.bcbss.applvl = aa.bcbss.applvl +1
'Clear out existing scheduled scripts to "scpCheck_Closeit".
for j = 1 to 10
	if script_schedule_name_get(j) = "scpCheck_Closeit"
		script_schedule("","",j)
	end if
next j
END FUNCTION

Tom

[russnobbs]

Re: Failed to Save Documents

Thanks,

The global variable may be the solution and probably a very good idea as I want to create a menu structure to get to all the various A5 apps we build at this location. I want to use buttons to move from one app to another.

Yes, all the databases are in g:\database\data\someapp.adb format.

The paths worked (and continue to work) running under A5 V7. It's under A5V10 that I get the error. From the A5 more databases file open menu browsing to the directory and file it works fine.

I'm the user and I have full rights to all drives. I thought that the file open code might have changed between V7 and V10 to force a save and close on the open app and that gave me the Failed to Save Documents error. But I don't recognize any thing unsaved as I reach the button. I'll keep fussing with it.

[Clunes]

Re: Failed to Save Documents

can you post a view of the script. If it is an action script, click the spectacles and then screen snapshot.

This may help to show why it is getting an error

[Mike Wilson]

Re: Failed to Save Documents

"Failed to save document" on startup
I have this periodically for my A5v10.5 app. Don't know why. Multi-user app, only affects my developer A5 not RunTime which all else using. I am able to clear this by opening the app in A5v11 and immediately closing it. Then opening it in v10 developer the "Failed to save document" on startup doesn't manifest. It seems to be something that is being detected with v10 developer sensing the app is still open and wasn't closed down properly, so requires opening in another version and closing down from the other version to get the app to be sensed by v10 as fully closed. I have found no other way to clear this. Thankfully I found this. Someone must know which app file (.alx,.alb,adb,etc) contains the "flag" that the startup process is reading as the app is "already open".

[Tom Henkel]

Re: Failed to Save Documents

We get it on both runtime and developer versions in both ver 10.5 and ver 12. It only happens on our non-shadowed apps residing on the server. My gut feeling is that it is a timing issue. Haven't been able to get past it except with a shadow.

Tom