Backend problem

Jazzwineman gatwickdp at britmail.net
Sun Jan 22 18:29:39 EST 2017


David Carlson-4 wrote
> It sounds like you are keeping your data files in one of the database
> formats but you did not install the database engine in the Ubuntu box that
> gives you the error message.
> 
> There is more than one way to solve that problem.  The easiest is to
> switch
> to the default compressed XML data format (.gnucash).   The other is to
> install the correct database engine for your data type.  I have never done
> the latter myself and the wiki was just reorganized so I cannot find the
> reference to look at for instructions.  Hopefully someone who uses a
> database format in Linux will tell us how to do that.
> 
> 
> David C
> 
> On Sun, Jan 22, 2017 at 4:48 PM, GatwickDP <

> gatwickdp@

> > wrote:
> 
>> the gnucash files that are on the win10 machine and then on the ubantu
>> machine open up gnucash and attempt to open the files on the win10
>> machine-
>> we get the bankend error message.
>>
>> This does not happen on any other ubantu machine or on a winxp machine.
>> Purely as a test, I installed gnucash on the win 10 machine and opened
>> the
>> files that had been stored on the win 10 machine - just to see if they
>> were
>> corrupt or any such thing and they opened fine. I also ran the gnucash
>> from
>> win 10 and opened files that were on the ubantu machine and thus the only
>> problem is getting the silly back-end message when opening the gnucash
>> program on ubantu and then trying to run the files that are stored on
>> win10.
>>
>> --- 

> clanlaw@

>  wrote:
>>
>> From: Colin Law <

> clanlaw@

> >
>> To: 

> gatwickdp@

>> Cc: "

> gnucash-user@

> " <

> gnucash-user@

> >
>> Subject: Re: Backend problem
>> Date: Sun, 22 Jan 2017 21:13:16 +0000
>>
>> On 22 January 2017 at 20:24, GatwickDP <

> gatwickdp@

> > wrote:
>> >    Here is the situation. Have Ubantu/32 box. Backup a number a files
>> to
>> >    make a mirror each day.
>> >    One of the folders is Gnucash with all the files and databases in
>> >    single folder. Works fine on local machine, can open program  and
>> mount
>> >    another computer (Ubantu) and go to data files there and Gnucash
>> works
>> >    fine. Works fine with all versions we are using of Ubantu and a Win
>> XP
>> >    machine.
>> >    Problem is when we created the exact same folder structure and put
>> it
>> >    on a Win 10 Pro 64  creating proper sharing/security structure on
>> Win
>> >    10 machine- when we  attempt to open Gnucash and we get the "no
>> >    suitable backend" error.
>>
>> I don't fully understand what you mean by that. Where are you running
>> Gnucash in the above situation? I assumed you meant you had installed
>> GC on the Win machine, but then in the first sentence below you say
>> that if you install GC on the Win machine it works ok.
>>
>> Please clarify exactly what is the situation that does not work.
>>
>> Colin
>>
>> > However when installing on the same win 10
>> >    machine a Gnucash program the files in the same folder open fine.
>> >    Further we can use the win 10 program and map/mount a drive from one
>> of
>> >    the Ubantu boxes and it opens fine.
>> >     All other files On Win 10, such as excel or word will open under
>> Libra
>> >    office quite fine from the ubantu box.
>> >    What are we missing and what gives?
>> >      __________________________________________________________________
>> >
>> >    http://www.britmail.net - The easy to remember, truly British email
>> >    address
>> >    http://www.britstuff.net - your one stop portal for all things
>> British
>> > _______________________________________________
>> > gnucash-user mailing list
>> > 

> gnucash-user@

>> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> > -----
>> > Please remember to CC this list on all your replies.
>> > You can do this by using Reply-To-List or Reply-All.
>>
>>
>>
>>
>> _____________________________________________________________
>> http://www.britmail.net - The easy to remember, truly British email
>> address
>> http://www.britstuff.net - your one stop portal for all things British
>> _______________________________________________
>> gnucash-user mailing list
>> 

> gnucash-user@

>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> -----
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>>
> _______________________________________________
> gnucash-user mailing list

> gnucash-user@

> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

I must be missing something in your suggestion. The original ubantu
computers that are being used have zero problems with opening any of the
gnucasf files on them, so apparently the database engine has to be correct.
Take any of the ubantu machines that have gnucah app on them and they can
open the files that are local to that machine or on another networked ubantu
or win xp machine. The exact same files are on the win 10 machine and only
on that machine does the attempt from a networked ubantu trying to open the
files on the win10  do we get the backend error. The files have to be fine
when as a test i open then with an app native to win 10 and the win 10 app
can open any of the data files of gnucash on any of the other networked
ubantu or winp machines . The only problem is that I open gnucash on a ubanu
computer and by the network try to open the data files that are on win 10.
Other machines See everything fine on win 10 - any other file from any other
program will open. Only problem is the gnucash. We are trying to use win10
as a mirror so that if one of the machines holding a number of files and
gnucash being only one set, we can just mount the drive from win 10 and go
down the road.



--
View this message in context: http://gnucash.1415818.n4.nabble.com/Backend-problem-tp4689079p4689096.html
Sent from the GnuCash - User mailing list archive at Nabble.com.


More information about the gnucash-user mailing list