pilot-db-list

Re: [pilot-db-list] How do I get pilot-db to work again?

[Fab <kr...@bi...>]

> Is there progress being made towards DB returning to being a pretty
> stable application?

	When I test a new beta I do some simple actions to
get back to the stable release. Today stable release is 0.3.3
which doesn't handle calculated fields. So, I only have one
db for test (named Test :-) which holds all new types. Other
dbs are real life ones with my data.
	When I get a new beta, I do a full backup. Then install
the new beta version, and play with it with only the test db. I
never try to open real life databases. I just accept to link to
them with "link" or "linked" types. During the runs, I write down
problems to report on the list, trying to find systematic ways of
reproducing fancy behaviours.
	After playing around with features I reinstall stable
release. With recent ones I also reinstalled the pdb which holds
categories, to make sure :-)
	Doing so I can test new betas, see the power of new
features, give my advice on some implementation choices, preserve
my databases and get a functionning program back for the next
real day :-)

	Don't forget, betas are unstable versions made to get
all the power of multi-testers phase. You can't hope them to
be fully functionnal. That's the way it goes.

	For your problems, my advice is : make a full backup of
your device, labeled "BadSatge" or something like that. Then,
delete all DB databases, DB program and DB related databases, either
whith the sync processor (better if your device still works a
little) whith a program like filez (freeware, see palmgear). Then
reinstall the stable version and then databases one after another,
trying them after each install.

	HTH.

	Fab.

Re: [pilot-db-list] How do I get pilot-db to work again?

[Larry K. T. <LK...@we...>]

Also as a default db does not backup the databases.  You have to select thi=
s for every database.  If you lose one on the handheld and you don't have i=
t backed up. It's gone.

I wish the default was to backup the database unless you specified otherwis=
e.

Larry

>>> Scott Wallace <swa...@my...> 01/24/02 10:49AM >>>

This is a great idea, and should ensure that you never loose important=20
data when you test out a new version.  At the very least, make sure you do=
 a full backup in case any files get corrupted.

By trying to support as many OS version as we do, we really rely quite a=20
bit on the beta testers.  Thanks for all your help, a stable version=20
should be on its way soon.

	-Scott

On Thu, 24 Jan 2002, Fab wrote:

> > Is there progress being made towards DB returning to being a pretty
> > stable application?
>=20
> 	When I test a new beta I do some simple actions to
> get back to the stable release. Today stable release is 0.3.3
> which doesn't handle calculated fields. So, I only have one
> db for test (named Test :-) which holds all new types. Other
> dbs are real life ones with my data.
> 	When I get a new beta, I do a full backup. Then install
> the new beta version, and play with it with only the test db. I
> never try to open real life databases. I just accept to link to
> them with "link" or "linked" types. During the runs, I write down
> problems to report on the list, trying to find systematic ways of
> reproducing fancy behaviours.
> 	After playing around with features I reinstall stable
> release. With recent ones I also reinstalled the pdb which holds
> categories, to make sure :-)
> 	Doing so I can test new betas, see the power of new
> features, give my advice on some implementation choices, preserve
> my databases and get a functionning program back for the next
> real day :-)
>=20
> 	Don't forget, betas are unstable versions made to get
> all the power of multi-testers phase. You can't hope them to
> be fully functionnal. That's the way it goes.
>=20
> 	For your problems, my advice is : make a full backup of
> your device, labeled "BadSatge" or something like that. Then,
> delete all DB databases, DB program and DB related databases, either
> whith the sync processor (better if your device still works a
> little) whith a program like filez (freeware, see palmgear). Then
> reinstall the stable version and then databases one after another,
> trying them after each install.
>=20
> 	HTH.
>=20
> 	Fab.
>=20
>=20
> _______________________________________________
> Pilot-db-list mailing list
> Pil...@li...=20
> https://lists.sourceforge.net/lists/listinfo/pilot-db-list=20
>=20

--=20


_______________________________________________
Pilot-db-list mailing list
Pil...@li...=20
https://lists.sourceforge.net/lists/listinfo/pilot-db-list

Re: [pilot-db-list] How do I get pilot-db to work again?

[Scott W. <swa...@my...>]

On Thu, 24 Jan 2002, Larry K. Turner wrote:

> Also as a default db does not backup the databases.  You have to select this for every database.  If you lose one on the handheld and you don't have it backed up. It's gone.
> 
> I wish the default was to backup the database unless you specified otherwise.


Yes, it is already in the current working code. ;)

	-Scott

Re: [pilot-db-list] How do I get pilot-db to work again?

[Scott W. <swa...@my...>]

This is a great idea, and should ensure that you never loose important 
data when you test out a new version.  At the very least, make sure you do 
a full backup in case any files get corrupted.

By trying to support as many OS version as we do, we really rely quite a 
bit on the beta testers.  Thanks for all your help, a stable version 
should be on its way soon.

	-Scott

On Thu, 24 Jan 2002, Fab wrote:

> > Is there progress being made towards DB returning to being a pretty
> > stable application?
> 
> 	When I test a new beta I do some simple actions to
> get back to the stable release. Today stable release is 0.3.3
> which doesn't handle calculated fields. So, I only have one
> db for test (named Test :-) which holds all new types. Other
> dbs are real life ones with my data.
> 	When I get a new beta, I do a full backup. Then install
> the new beta version, and play with it with only the test db. I
> never try to open real life databases. I just accept to link to
> them with "link" or "linked" types. During the runs, I write down
> problems to report on the list, trying to find systematic ways of
> reproducing fancy behaviours.
> 	After playing around with features I reinstall stable
> release. With recent ones I also reinstalled the pdb which holds
> categories, to make sure :-)
> 	Doing so I can test new betas, see the power of new
> features, give my advice on some implementation choices, preserve
> my databases and get a functionning program back for the next
> real day :-)
> 
> 	Don't forget, betas are unstable versions made to get
> all the power of multi-testers phase. You can't hope them to
> be fully functionnal. That's the way it goes.
> 
> 	For your problems, my advice is : make a full backup of
> your device, labeled "BadSatge" or something like that. Then,
> delete all DB databases, DB program and DB related databases, either
> whith the sync processor (better if your device still works a
> little) whith a program like filez (freeware, see palmgear). Then
> reinstall the stable version and then databases one after another,
> trying them after each install.
> 
> 	HTH.
> 
> 	Fab.
> 
> 
> _______________________________________________
> Pilot-db-list mailing list
> Pil...@li...
> https://lists.sourceforge.net/lists/listinfo/pilot-db-list
> 

-- 

Re: [pilot-db-list] How do I get pilot-db to work again?

[Harald Hanche-O. <ha...@ma...>]

+ Fab <kr...@bi...>:

| Today stable release is 0.3.3

http://sourceforge.net/projects/palm-db-tools/ still lists 0.3.2 as
the latest.  Maybe the page needs updating?

- Harald