Dixon, many thanks for your help.
On 11/09/2015 20:21, 'E. D. Epperson Jr' dixonepper...@gmail.com
[firebird-support] wrote:
At work and don't have Windows 10 or FirebirdSql here, so I can't test
my theory. But I suspect its permissions related.
There is a new feature on the properties dialog
At work and don't have Windows 10 or FirebirdSql here, so I can't test my
theory. But I suspect its permissions related.
There is a new feature on the properties dialog for files in Windows 10.
Its a checkbox to unblock a file. Right click on the security.fdb, select
Properties and see if that
On 11/09/15 21:29, Mike Ro miker...@gmail.com [firebird-support] wrote:
>> On a more radical solution, try installing your firebirdsql to a
>> folder NOT in Program Files.
>>
> Yes, this solves it!
>
> So it is definitely a permissions thing, but I haven't been able to find
> out what yet.
Hello
Something I have noticed with Firebird v2.1 with Windows 32 & 64 bit
Superserver & Classic and is that the security2.fdb file grows
substantially and keeps on growing.
We use just a single user for database access.
I have one system at the moment where it is 50Meg but have seen
Hi Neil,
Run DBInfo from IBSurgeon Free tools and check what pages are there.
I suppose there are many TIPS, which indicate transactions.
Verify it with gstat -h transaction markers values.
Regards,
Alexey Kovyazin
IBSurgeon
Hello
Something I have noticed with Firebird v2.1 with Windows 32
I am trying to install a Firebird server on a reasonably clean Windows
10 machine, but I am running into the gsec "cannot attach to password
database" issue.
Details are:
Edition: Windows 10 Pro (64-bit system, x64 based processor)
Firebird: SuperServer - both 32-bit and 64-bit versions