I'm asking that question as I'd like to try a strategy :
- when an IQ instance is busy calculating stuff (hence, frozen), I was thinking that maybe I could open another instance and continue my work...
Is that risky ? What could happen ?
Comments
IQ uses JET as its database engine which is fully multi-user. Also, each field value is a separate database record, hence reducing the data corruption risk. So the bottom line is, no, the only possible situation is that the second instance gets an inconsistent / outdated set of field-values. Nothing that a refresh would not solve...
IQ uses JET as its database engine which is fully multi-user. Also, each field value is a separate database record, hence reducing the data corruption risk. So the bottom line is, no, the only possible situation is that the second instance gets an inconsistent / outdated set of field-values. Nothing that a refresh would not solve...
[/quote]
Thanks. This is good to know. I already asked the question once, but wanted to have some kind of confirmation as this was more than 2 years ago.
Another related question : what about changes made to the "This Database" User code and other grid configuration changes ?
(I'll put all the info in the manual afterward...)
All grid changes are saved on a refresh, so the other IQ instance grids will behave exactly as when you have the same grid opened more than once
The user code is loaded on startup (system, user) or when opening file (DB specific), so changes in one IQ instance is not updated in the other. Idealy, the program should monitor changes to these file and reload the code, but this is not implemented yet.
The user code is loaded on startup (system, user) or when opening file (DB specific), so changes in one IQ instance is not updated in the other. Idealy, the program should monitor changes to these file and reload the code, but this is not implemented yet.
[/quote]
(My emphasis...)
So, yes that would be great. I started working with 2-4 instances and I like it. The only problem is that if I make a change in the VB code I need to close + rerun the whole thing, or paste the same bits of codes in all instances. It's all feasible, but not very practical.
Let's say a user wants two of the same view; not sure why, but hypothetically. Does user have to construct the 2nd one & give it a separate name or is there a clone tool that applies to grid? (might add on numerical value automatically like duplicate file saves...)
Let's say a user wants two of the same view; not sure why, but hypothetically. Does user have to construct the 2nd one & give it a separate name or is there a clone tool that applies to grid? (might add on numerical value automatically like duplicate file saves...)
[/quote]
You know that you can have several "windows" of the same grid, right ?
Or are you talking about actually "copying" a grid to have an identical one with its own entry in the grid management dialog ? If this is what I think you mean, I think it's more or less in Mantis :
OK, thanks, Armando. Sorry to have confused matters. I guess I was also wondering -- under your scenario -- whether another window of the same grid would also permit continued work (instead of opening a duplicate dB), but I guess not.
OK, thanks, Armando. Sorry to have confused matters. I guess I was also wondering -- under your scenario -- whether another window of the same grid would also permit continued work (instead of opening a duplicate dB), but I guess not.
[/quote]
Yes, it would work, theoretically, but if IQ is frozen because it's calculating stuff (which you might not experience... But I do because I have many equations running in the background), the only solution is to open an other instance... Which is a bit like having a multi threaded IQ.
Comments
New feature