PureBasic Forums - English

No prefs, virgin environment, no session history, still happened. Maybe scintilla?

Can you call a module from within a module? I tried to do that and got an error "Module not found (and the details)". I can call from the main without problem. Or am I doing something wrong?



DeclareModule mod1
Declare func1()
EndDeclareModule
Module mod1
Procedure func1()
Debug "mod1 ...

Apparently this is redundant, dateEx handles it.

I had to parse some date formats for a syslog server I wrote. It's been in use for a while, but really, rather limited in use in terms of what it does/handles on a regular basis
This handles a lot more than standard formatdate() tkens %yyy%/%hh etc. as well as parsing those dates.

Maybe someone ...

Curious. I guess do a search & replace on "days" to "180" .

Here is a simpled example. Note, this example has saving any changes commented out
EnableExplicit
UseSQLiteDatabase()

#file$ = "c:\temp\dump\d\backup\history.db"
#daysOld=180

Debug "Removing records older than "+Str( #daysOld )+" days ...

The database hasn't remained large (the file is now only 144 MB compared to 757 MB), but why does the debug output say "Removing records older than 365 days" when I told it to only remove older than 180 days? Has it kept history that I didn't want? I know nothing about SQLite.


How did you ...

the id's are generated automatically.
Did you see the examples networkClient.pb and networkServer.pb?

Over time, database files can grow. Leaving empty space.

Do this, before the 'vacuum'
If DatabaseQuery(db,"pragma freelist_count")
If NextDatabaseRow(db)
Debug "Free count "+FormatNumber(GetDatabaseLong(db,0),0)
EndIf
FinishDatabaseQuery(db)
EndIf


I'm betting it's a rather large #.
The ...

Old post, but I'm working on a more robust cleaner (removing invalid/corrupt records, mismatched records, etc)

In case anyone else wants to, here's a simple way to remove older records:

UseSQLiteDatabase()
Declare removeOlder( cHistoryDB.s, days=-1 )

removeOlder( "c:\temp\dump\d\backup\history ...

This is some older code, and needs updating, but it might get you started... this is not my code.

; after
; https://msdn.microsoft.com/en-us/library/windows/hardware/ff563620(v=vs.85).aspx
; https://stackoverflow.com/questions/38102565/how-can-a-vb-6-app-determine-if-it-is-running-on-windows-10 ...

Or keep it simple... (now with thread demo) (assuming you don't need the size in one location, just from individual threads)

EnableExplicit

Procedure.q FolderSize(dir$)
Protected size.q, dir
dir=ExamineDirectory(#PB_Any,dir$,"")

If dir
While NextDirectoryEntry(dir)
If DirectoryEntryType ...

(I'm using 6.11b3 x64, didn't try x86)
run this under C backend, then ASM backend. Will the backends ever agree on math, or are workarounds the norm?

Could not find a wiki article on this... so I hope this isn't redundant or already implemented (sorry if it is)

when you enter a PB command [eg: OpenDatabase()] a statusbar entry pops up at the bottom (in addition to parameters, it shows a description: "Opens the specified database")

in a shared ...

Less than ideal. Requires a modicum of cooperation not always easy, or reliable.

How can I work around this? (without knowing the what the other did)
I had done something like: Enumeration #PB_EventType_FirstCustomValue+1000, but this leaves open manual collisions by chance.

DeclareModule abc
Declare xyz()
EndDeclareModule
Module abc
Enumeration #PB_EventType ...