Hi,
So my situation can be summed up as follows:
After years of tedious search for "my" all-in-one pim, notetaker, organizer, task/project/information manager, outliner ... , reading lots of program descriptions and even more forum discussions - such as donationcoder, outlinersoftware and similar - after a number of disappointing practical efforts with quite a number of programs, such as eccopro in particular I finally decided that infoqube must be what comes closest to what I'm looking for.
But unfortunately I cannot get infuqube to work. I can start Infoqube OK - empty, without database. I can create a new file, and I can save it. But when I want to (re)open a file the program hangs and I can't do anything but force it to close using the task manager. But I cannot start Infoqube by clicking on a database file icon.
After having done that I find an ldb-file in the application data folder of my userprofile in Windows 2000 workstation. This file has the same name as the database file I created. The date which is the same as date and time of the creation is changed when closing. This happens everytime I create a file with infoqube.
It is usual for MS Access (2000 through 2007 afaik) to create such a ldb-file in a multiuser setting in order prevent one user from changing a database that is in the proess of being changed by another. It is also usual for MS to delete the ldb file after the database has been closed. It is also known that in case this ldb-file remains undeleted after closing the database this can cause problems accessing the database.
After years of tedious search for "my" all-in-one pim, notetaker, organizer, task/project/information manager, outliner ... , reading lots of program descriptions and even more forum discussions - such as donationcoder, outlinersoftware and similar - after a number of disappointing practical efforts with quite a number of programs, such as eccopro in particular I finally decided that infoqube must be what comes closest to what I'm looking for.
But unfortunately I cannot get infuqube to work. I can start Infoqube OK - empty, without database. I can create a new file, and I can save it. But when I want to (re)open a file the program hangs and I can't do anything but force it to close using the task manager. But I cannot start Infoqube by clicking on a database file icon.
After having done that I find an ldb-file in the application data folder of my userprofile in Windows 2000 workstation. This file has the same name as the database file I created. The date which is the same as date and time of the creation is changed when closing. This happens everytime I create a file with infoqube.
It is usual for MS Access (2000 through 2007 afaik) to create such a ldb-file in a multiuser setting in order prevent one user from changing a database that is in the proess of being changed by another. It is also usual for MS to delete the ldb file after the database has been closed. It is also known that in case this ldb-file remains undeleted after closing the database this can cause problems accessing the database.
I am working in a multiuser setting in a Windows 2000 Server Professional network with a few workstations and roaming profiles. I work with several programs which use MS Access as their data base. Every once in a while I work with Access databases directly. But this problem with MS Access Data bases occurred never before. Never before did I see an ldb-file in my system even though lots of Access Data bases are open simultaneously. That could be due to the privileges users have in my system.
Never before did I encounter any problems installing software on my system, software using MS Access in particular.
During my search as to what could be the cause of my problem I found a tool that can read ldb files. ( The Access Workbench from vb123.com) It obviously makes use of the jetutils package provided by MS which is too difficult for me to handle directly.
It said the following (with database closed):
"DATABASE IS REPORTED AS OPEN IN EXCLUSIVE MODE - The List of users is not available.
This warning occurs when someone has opened the database object in exclusive mode or opened a form or report in design mode. It can also occur if you are using the incorrect workgroup/username."
The tool cannot open the database first because the ldb file was still present, then - after I erased it - because it does not have the suffix "mdb" but "sndb" instead.
When I changed the database suffix to mdb and tried to open the database with this tool or MS Access I was told that the database has an unknown format. This could be due to the fact that it was created with a version later than Access 2000 so that the database format cannot be read.
I also attached the errorlog file to my first post. But apparently that does not provide any clue as to what's going on here. Here's what it says:
"DATABASE IS REPORTED AS OPEN IN EXCLUSIVE MODE - The List of users is not available.
This warning occurs when someone has opened the database object in exclusive mode or opened a form or report in design mode. It can also occur if you are using the incorrect workgroup/username."
The tool cannot open the database first because the ldb file was still present, then - after I erased it - because it does not have the suffix "mdb" but "sndb" instead.
When I changed the database suffix to mdb and tried to open the database with this tool or MS Access I was told that the database has an unknown format. This could be due to the fact that it was created with a version later than Access 2000 so that the database format cannot be read.
I also attached the errorlog file to my first post. But apparently that does not provide any clue as to what's going on here. Here's what it says:
07.01.2010 06:47:38 91 3 Main>LoadUserFunctions
07.01.2010 06:47:38 91 Objektvariable oder With-Blockvariable nicht festgelegt(l=0)
Main LoadUserFunctions ReadUserFunctions ReadFile
07.01.2010 06:47:38 91 3 Main>LoadUserFunctions
07.01.2010 06:47:38 91 3 Main>LoadUserFunctions
07.01.2010 06:47:38 91 Objektvariable oder With-Blockvariable nicht festgelegt(l=0)
Main LoadUserFunctions ReadFile ReadUserFunctions
07.01.2010 06:47:38 91 3 Main>LoadUserFunctions
07.01.2010 06:47:38 91 3 Main>LoadUserFunctions
07.01.2010 06:47:38 91 Objektvariable oder With-Blockvariable nicht festgelegt(l=0)
Main LoadUserFunctions ReadFile ReadUserFunctions
07.01.2010 06:47:38 91 3 Main>LoadUserFunctions
07.01.2010 06:47:38 91 3 Main>LoadUserFunctions
07.01.2010 06:47:38 91 Objektvariable oder With-Blockvariable nicht festgelegt(l=0)
Main LoadUserFunctions ReadFile
07.01.2010 06:47:44 91 3 Main>LoadUserFunctions
07.01.2010 06:47:44 91 3 Main>LoadUserFunctions
07.01.2010 06:47:38 91 Objektvariable oder With-Blockvariable nicht festgelegt(l=0)
Main LoadUserFunctions ReadFile MDIForm_Load
(nicht festgelegt = not defined).
I do not know what that means. But afaik a database is an object. 06:47:38 was the time the database was created. Maybe usually an object variable is defined doing this? 06:47:44 was the time the database was saved.
Could anyone please explain to me why this can NOT mean that my problem is simply an incompatability of infoqube databases with Access 2000?
If I could try the portable infoqube version, that might help to find out whether there could be any installation issues, because a problem like this is unheard of. So I was told.
Since I unfortunately cannot do that - the portable version does work for Win Xp up only which I do not have - I'd greatly appreciate if you could please rule out an incompatability of Access versions. If this should turn out to be my problem it must be dealt with anyway before you can distribute infoqube to users working with Office 2000.
Otherwise this would mean I will not be able to get infoqube to run on my machine or in my network
Could anyone please explain to me why this can NOT mean that my problem is simply an incompatability of infoqube databases with Access 2000?
If I could try the portable infoqube version, that might help to find out whether there could be any installation issues, because a problem like this is unheard of. So I was told.
Since I unfortunately cannot do that - the portable version does work for Win Xp up only which I do not have - I'd greatly appreciate if you could please rule out an incompatability of Access versions. If this should turn out to be my problem it must be dealt with anyway before you can distribute infoqube to users working with Office 2000.
Otherwise this would mean I will not be able to get infoqube to run on my machine or in my network
sfinxx (unhappy)
Comments
But there's a reason, why I'm a bit impatient. I don't have too much time - as everybody else. I'll have some "spare" hours within the next few days. I wanted to use them to get infoqube to work for me. If I can't do it now, it may very well be that I'll not be able to do it for a long time.