Fermer I. aldweb

Fermer II. Gratuitiels PC

Fermer III. Gratuitiels Palm

Fermer IV. Partagiciels Palm

Fermer V. iziBasic Palm

Fermer VI. Connaissance Palm

Fermer VII. Ordinateur Poche

Fermer VIII. miniPortail

Spécial !

Version mobile
de l'aldweb Site

Ni Français, ni Anglais ?

Essayez donc l'un de ces drapeaux :
[de] [es] [it] [pt]

Météo / Spam / www

Météo Lyon

aldweb contre le SPAM

Pour avoir des nouvelles de ce site, inscrivez-vous à notre Newsletter.
Se désabonner
298 Abonnés
Sites web de la famille

Webmaster - Infos
News Amis


   visiteurs en ligne

Comment trouve-tu le nouvel habillage de l'aldweb Site ?
Superbe !
forum.gifForum - iziBasic - Sujet n°1062

Forum - Forum
iziBasic - iziBasic

Warning: A non-numeric value encountered in /web5/aldweb/www/aldweb_com/www/thread.php on line 257

actif  Sujet n° 1062  File Efficiency

le 18/01/2005 @ 22:51
par Chuck


Using the single number per record approach like iBAddress, my database used about 6k on my m505. Now it uses 122k on my Treo 650. I know this is due to Palm's new memory structure in the Treo and T5. I need to write my database more efficiently.

In the documentation, it says everything is stored as text. How many characters are used to store positive and negative numbers, dates, etc.? Since my numbers are usually -xx.xx, would I be better off saving this view (6 chars) or the default storage method?

I am assuming that I will have to manually build/parse my 8 values as a single record. Any hints, limitations or things to watch out for? Maximum record length? Illegal characters? Any guidance is appreciated.
  Poster une réponse  Haut

Warning: A non-numeric value encountered in /web5/aldweb/www/aldweb_com/www/thread.php on line 497
Réponse n° 1
le 18/01/2005 @ 23:35
par aldweb


Hello Chuck,

So, let me try to give you some hints.

The best way for you, I guess, would be to use the MegaString to store your records.
MegaString was introduced in version 4.0 of iziBasic more or less having the T5 and Treo 650 in mind

Then, you may save your data in it, using a field separator character of your liking (or fixed size fields, it is up to you) and you may even define the format for your numbers as you want, with all the available functions in iziBasic (to convert from number to string).
Of course, reading back a record will require a small routine to parse the MegaString.
This is the best way to limit the side effect of the Treo 650 and T5.

Before using the MegaString, which is 4KB big, you may train yourself with a standard string variable, but your record will have to be no more than 62 (or 63, I never remember!) characters long.
But, 62 characters will be completed to 512 characters by your device... So, really better use the MegaString if a record can, by any chance, be bigger than 62 characters.

Here is a small and dummy source code that will write 10 lines filled with 10 numbers (1 to 10!) formated "x.xx" in a Memo, using the MegaString. CHR$­­(10) could be considered as a field separator character even though it is a real line feed in the Memo Pad application.
FOR I=1 TO 10
PUTSTRING$­­$­­ A$­­,J
PRINT$­­$­­ #1

I hope my first explanations will help you. Otherwise, just ask for more


Ecrire à aldweb   Poster une réponse  Haut
actif sujet actif   clos sujet clos   Important! Important!   Nouveau Nouveau message   -   Rectifier Rectifier message   Clôturer Clôturer sujet   Remonter Remonter
Catégories de discussion  Forum 

^ Haut ^