Hi Chris
Thanks for that - must have picked that up from somewhere else
From what Mike said regarding the block sizes and max file size, in the command
iscr32.exe -k24 -r3000 test.pro
should it be 3000 or 3072 ?
Just want to be clear.

file size
Started by
Guest_Guest_guest_*
, Feb 22 2005 01:37 AM
19 replies to this topic
#18
Guest_Guest_*
Posted 25 February 2005 - 03:46 PM
Dan, Joseph,
I don't actually think it's an unreasonable opinion at all
I've suggested to ProIV on more than one occasion that they should make it possible to deploy the runtime bootstrap subset (ie. this doesn't apply to development) into a database (I'm interested in Oracle).
This would make production systems simpler to manage and potentially more reliable because one can eliminate ProISAM completely. It's of particular interest when deploying a "parallel" application - where the same ProIV app code needs to run on multiple physical machines accessing the same database.
What's needed technically is pretty much already in place in ProIV, but you really also need "function caching" (which has been "on the way" for ages but apparently still isn't included in V6) to take up any performance hit.
ProIV's possibly correct view is that this is not of interest to many customers.
Just an unreasonable opinion based on nothing but snobbery:
The maximum size for a PRO-ISAM file in any self-respecting production application ought to be 0 bytes.
That creates quite a burden for logic.pro and genfile.pro!
I don't actually think it's an unreasonable opinion at all

I've suggested to ProIV on more than one occasion that they should make it possible to deploy the runtime bootstrap subset (ie. this doesn't apply to development) into a database (I'm interested in Oracle).
This would make production systems simpler to manage and potentially more reliable because one can eliminate ProISAM completely. It's of particular interest when deploying a "parallel" application - where the same ProIV app code needs to run on multiple physical machines accessing the same database.
What's needed technically is pretty much already in place in ProIV, but you really also need "function caching" (which has been "on the way" for ages but apparently still isn't included in V6) to take up any performance hit.
ProIV's possibly correct view is that this is not of interest to many customers.
#20
Posted 17 March 2005 - 07:33 AM
Hi,
Use the ischk utility.
eg,
This gives you the page size and other info about the file.
Rob D.
Use the ischk utility.
eg,
ischk -v logic.pro
This gives you the page size and other info about the file.
Rob D.
Reply to this topic

0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users