|
Sounds to me like classic running out of resources. I've never seen a serious app which needed 50 MultidocTemplates, never mind 150, but there you go, there's always a first for everything. Then on top of that you try and run multiple instances of this. (More than 3 anyways). Sounds more like a test of how much abuse you can give the system before it breaks. BTW how many documents of each of the 150 types did you plan to have open at the same time in the multiple instances, and what would the average size of each document be.
It sounds to me like a case of 'Back to the Drawing Board'
Hope this is Helpful 
Bram van Kampen
|
|
|
|
|
First... this is the 3rd or 4th time I see the question, if you are the same user repeating question, you could tae a look to the answers of your previous posts. If not... take a look on them, maybe you find the solution.
Second... Why do you want to make different instances of application? Can't you just make, different pairs Doc-View in just one instance of your application?
Greetings.
--------
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
“The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson
|
|
|
|
|
Hi Chirag,
Did you found a solution, I am running into the same issue.
Thanks,
Priyank
|
|
|
|
|
Hello,
I have read an excel sheet through IDispatch interface in VC++.
But still I have not understood the fundamentals of IDispatch.
What is this interface ?
Is IDispatch a class ?
Why the same IDispatch pointer can be used for the classes Application,Workbook,Range etc?
Is there any link to understand these concepts?
Prithaa
|
|
|
|
|
prithaa wrote: Is there any link to understand these concepts?
No. And if there were you certainly could not find them by using Google to search for them.
|
|
|
|
|
You're so bad!
¡El diablo está en mis pantalones! ¡Mire, mire!
Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)!
SELECT * FROM User WHERE Clue > 0
0 rows returned
Save an Orange - Use the VCF!
VCF Blog
|
|
|
|
|
IDispatch and IUnknown are fundamental COM interfaces. Read up on COM, Interfaces, and dual interfaces (IDispatch is used for dual interfaces), as well as the specific IDispatch and IUnknown interface documentation.
Very generally speaking, IDispatch is used for scripting like/interpreted languages (like VB) that will not have the methods statically bound at compile time. Instead, the methods are "bound" (or looked up) at run time and IDispatch provides the interface methods that describe how this is supposed to happen. The actual implementation of IDispatch is up to the application or library author.
¡El diablo está en mis pantalones! ¡Mire, mire!
Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)!
SELECT * FROM User WHERE Clue > 0
0 rows returned
Save an Orange - Use the VCF!
VCF Blog
|
|
|
|
|
Thanks everybody for your answers.
Prithaa
|
|
|
|
|
For C++ developers to understand COM I highly recommend the book Inside Com - Dale Rogerson[^]
This is one of the best books I ever read, period.
|
|
|
|
|
led mike wrote: This is one of the best books I ever read
I never thought I'd ever hear anyone ever say that about a COM book.;P
Anyone who can chew up COM (in C++) and still laugh... I'm speechless.
|
|
|
|
|
Hey all,
I have implemented a simple TCP server/client class from the following web-site
(http://www.codeproject.com/internet/winsockintro02.asp). Which shows us how
to send raw char* data over the TCP connection.
My problem is that I want to be able to send a whole instance of a class, for example
ClassFoo objectFoo; i.e. I want to be able to send the object:
<br />
objectFoo , instead of just text, i.e. "hello".
Can anyone help me, by hinting how to achieve this ?
Thanks
|
|
|
|
|
You need to do what is frequently referred to as "Marshalling", in other words, you need to convert an instance of your class into a byte stream, and then, when you recv this byte stream from a source, you need to be able to "reconstitute" it. Look up marshalling for ideas on how to do this. COM supports this and performs it automatically (as well as allowing you to customize the process if you're crazy enough). I think .Net supports this as well. There are C++ frameworks that also support this, you can look for them.
¡El diablo está en mis pantalones! ¡Mire, mire!
Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)!
SELECT * FROM User WHERE Clue > 0
0 rows returned
Save an Orange - Use the VCF!
VCF Blog
|
|
|
|
|
Jim Crafton wrote: You need to do what is frequently referred to as "Marshalling"
 Isn't marshalling used in terms of memory where reconstituting objects is referred to as serialization?
|
|
|
|
|
Actually I was going to ask you the same question! I was going to say "serialization" but then I *thought* (always a dangerous idea) that serialization was just a way to store object data, not necessarily create a new object from scratch. Whereas marshalling was actually the ability to send the object across the wire with all the info needed to completely recreate it from scratch on the other side.
Now that I think about it, I suspect I'm getting my "definition" from how COM does things, which may or may not be the way most other OO frameworks/libraries do things.
¡El diablo está en mis pantalones! ¡Mire, mire!
Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)!
SELECT * FROM User WHERE Clue > 0
0 rows returned
Save an Orange - Use the VCF!
VCF Blog
|
|
|
|
|
Jim Crafton wrote: Now that I think about it, I suspect I'm getting my "definition" from how COM does things, which may or may not be the way most other OO frameworks/libraries do things.
Well I just checked an according to the Wikipedia they are interchangeable. From my experience I learned about marshalling way back in Remote Procedure Calls and Serialization came later in terms of Objects so I made the connection that way. Learn something new everyday.
|
|
|
|
|
bigdenny200 wrote: Can anyone help me, by hinting how to achieve this ?
It's called "Serialization". You might want to use it as a keyword in Google and read some material to gain a basic understanding of it.
|
|
|
|
|
Dear led,
thanks for reply. I found a tutorial, which should have done a serialization, as you suggested.
Below is the code (with my object, instead the one from tutorial):
std::vector<std::string> word_list;
word_list.push_back(_T("HI"));
ofstream ofs("c:\\fifthgrade.ros", ios::binary);
ofs.write((char *)&word_list, sizeof(word_list));
std::vector<std::string> word_list2;
ifstream ifs("c:\\fifthgrade.ros", ios::binary);
ifs.read((char *)&word_list2, sizeof(word_list));
The problem is that this code (the last line) doesnt work. And I think this is
because I am using not simple Class instances, but a vector object.
Do you have any idea, what could be other reason for it not to work ?
thanks
|
|
|
|
|
bigdenny200 wrote: I found a tutorial
Please provide a link. Either it is not adequate or you have not understood it correctly. I would think most people would take longer than a single hour of studying to understand serialization. You are trying to understand it right? Not just trying to reproduce the tutorial source code for your purposes, that's not going to go well. You need to study it with the goal of understanding it.
|
|
|
|
|
I agree with what you are saying, but the problem is that I am working on a project which
is due soon. And I cant devote too much time to serialization only. But, in this case, I really thought that using the tutorial was supposed to work and would suffice.
Here it is: http://www.functionx.com/cpp/articles/serialization.htm,
and it seemed pretty easy for me from here.
Thanks
|
|
|
|
|
Yeah, I would not recommend that tutorial. The example "class" used is not a class, it is a simple 'C' data structure and there has been intrinsic support for reading and writing 'C' data structures since.... well 'C'. That is not the same thing as 'Serialization' of complex C++ classes that may contain pointers which are memory addresses.
You cannot serialize a memory address. You must serialize/deserialize the data at the memory address which requires knowledge of the data structure. Knowledge of the data structure is something that only the developer has meaning you cannot rely on the compiler to properly serialize your class.
bigdenny200 wrote: but the problem is that I am working on a project which
is due soon. And I cant devote too much time to serialization only.
I can't help the fact that poor project management and planning conflicts with reality. I am only a software developer not a magician that can bend time and warp reality. Perhaps your situation now calls for the Post Agile Manifesto approach to software development[^]. I don't recommend it, but if that's what you must do.... whatever.
|
|
|
|
|
> I can't help the fact that poor project management and planning conflicts with reality. I am >only a software developer not a magician that can bend time and warp reality. Perhaps your >situation now calls for the Post Agile Manifesto approach to software development[^]. I don't >recommend it, but if that's what you must do.... whatever.
There is no project management, its a University project. Had a lazy life before So now, I am tight in my deadlines.
|
|
|
|
|
bigdenny200 wrote: So now, I am tight in my deadlines.
Hmm....in the 5 hours this thread has been around, you probably could have researched and implemented serialization for
a class 
Whether or not you use MFC, I would take a look at Serialization (MFC)[^]
This is an example of a fairly robust, generic, serialization solution.
On the other (easy) end of the solution spectrum, you could simply add a serialize method and
an unserialize method to your class, both of which take a socket as a parameter.
The serialize method would write (binary) all the class' data, one at a time, to the socket.
The unserialize method would read the binary data into the class' members, in the same order it
was serialized. That's a simple, socket-only class serialization solution.
led mike...sorry for posting in your thread
Mark
Mark Salsbery
Microsoft MVP - Visual C++
![Java | [Coffee]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/coffee.gif)
|
|
|
|
|
Mark Salsbery wrote: On the other (easy) end of the solution spectrum, you could simply add a serialize method and
an unserialize method to your class, both of which take a socket as a parameter.
But that will ofcourse only work if the class contains no pointers or virtual functions. If you have already a successful way to save and retrieve to and from a file, your're nearly there if you have no virtual functions. Just use the same code to write to and retrieve from the socket.
Hope you get it together in time
Bram van Kampen
|
|
|
|
|
I'm trying to re-build my app and Im getting this error:
<br />
Linking...<br />
uuid.lib(oaidl_i.obj) : fatal error LNK1103: debugging information corrupt; recompile module<br />
Error executing link.exe.
???
I cant get why this is happening?
|
|
|
|
|
have you by any chance an instance of your application/dll still loaded in memory ?
also, have you tried a clean all/rebuild all ?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
