|
|
I want to save a linked list to an Access97 database. How do I do it in ADO.Net?
The following code doesn't compile/work..
CNode* pNode;
pDataRow->Item["ptrNode"] = &pNode;
I don't know what this compile error means "error C2102: '&' requires l-value"
Also Access97 has a "number" data type, can it store a pointer???
Can anyone help???
|
|
|
|
|
Saving a pointer to a node might not be such a good idea. The pointer is a physical address and that can change the next time the application is run. In a .NET application that can change while the application is running.
"On two occasions, I have been asked [by members of Parliament], 'Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able to rightly apprehend the kind of confusion of ideas that could provoke such a question."
--Charles Babbage (1791-1871)
My: Website | Blog
|
|
|
|
|
ooh yes, didn't think of that, thanks.
So do you know how to persist/save a linked list to Access97 ???
|
|
|
|
|
You can't save a linked list to a database. Either you have to serialize the entire list (which you probably have to do yourself), or save each item to a separate record.
---
b { font-weight: normal; }
|
|
|
|
|
Guffa,
Are you saying that if the entire linked list is serialised the system will maintain the links between the nodes, and I don't need to code/worry about it?
Do you know a code example of of a serialised linked list???
I was trying to save each node as a distinct record like your second suggestion. But how do you save the links using this option?
|
|
|
|
|
dragon_n_me wrote: Are you saying that if the entire linked list is serialised the system will maintain the links between the nodes, and I don't need to code/worry about it?
Yes, and no. References can't be maintained in any other form than a reference. If the list is serialized it will store the information about how the items are linked, and recreate the references when it's deserialized.
Do you know a code example of of a serialised linked list???
No.
I was trying to save each node as a distinct record like your second suggestion. But how do you save the links using this option?
You can't save references, you have to save some information that you can use to recreate the references.
---
b { font-weight: normal; }
|
|
|
|
|
To serialize, iterate over the linked list. Maintain a counter while you are iterating. Save each list item in the database along with the counter.
To deserialize, query the database for your list information, sorted by counter. Iterate over the list information, appending each record as a node to the end of your list.
-- modified at 23:57 Monday 10th July, 2006
|
|
|
|
|
I'm new to .Net but i've created a few windows apps however when i try and create a web project either C#.net or VB.net i get an error message "unable to create ...." and "http.1 error 500 " I'm using windows server 2003 and am not connected to any network, it's stand alone. With the old visual interdev i can create it with no problem. Has anyone ever come accross this or maybe have an idea as to what i can try.
none
|
|
|
|
|
You need to have IIS installed and running in order to create a web project in .Net 1.1.
|
|
|
|
|
Thanx mr_12345.
In fact i do have iis installed and running as a result I can create web projects using the old visual interdev, it only complains when i create one in the .net environment. I even tried uninstalling the old visual studio but with no luck.
none
|
|
|
|
|
Will an application created with VS2005 run with Windows 2000 or below?
---
With best regards,
A Manchester United Fan
The Genius of a true fool is that he can mess up a foolproof plan!
|
|
|
|
|
|
Yes, it will run on Windows 2000, but...
If your applications use any .NET features, then you need to install .NET runtime redistributable package to your Windows. The redistributable is free to download from Microsoft.
I never checked older Windows, like NT 4.0.
- It's easier to make than to correct a mistake.
|
|
|
|
|
Jun Du wrote: I never checked older Windows, like NT 4.0.
There isn't a NT4 runtime of .net2.0, 1.1 will run under NT4sp6a
|
|
|
|
|
Hi,
I've made a project to make Word documents with a template in VB.NET. If I try to make a preview of the page, my program craches and get an error in Word. It says:
"The assembly nederlandseTemp cannot be found in .\nederlandseTemp_bin\ or the assembly cannot be loaded. You can stil change and save the document."
nederlandseTemp was a second project in my solution, but I deleted it.
Has anyone any idea what's wrong with the solution?
Greetz Kris
|
|
|
|
|
solved the problem 
I needed to add an Office system project with name nederlandseTemp and select word Temp. Now he finds the file and opens office Word again.
greetz Kris
|
|
|
|
|
I have an application that was written in VB6 (lots of spaghetti code), that I am trying to get the business to upgrade to .net (redesign). What are some reasons that could be used to entice the business to upgrade?
I know the following:
1. Microsoft no longer supports VB6 so any future software releases (office, OS, etc.) could break functionality.
2. Maintenance Cost will be cheaper.
3. Fewer bugs due to better design, unit testing (nUnit)
Anyone got anymore?
Thanks in advance.
|
|
|
|
|
Well, fewer bugs are not guarenteed. If your current code is spagetti, it probably is a sign that the coding process needs to be improved, no language will do that. It also increases the odds that you'll have a really bad time trying to turn your code base into a VB.NET project.
I hate to say it, but an upgrade for it's own sake is not always a good idea. You may lose time trying to get back to the point you're at now ( that is, in converting to VB2005 ). You may introduce bugs. Unless you need stuff that's in the framework, or you just want to work in a supported framework, it's possible that upgrading is not a good idea.
Have you downloaded the VB Express Edition to see how your code fares in the upgrade process ?
Christian Graus - Microsoft MVP - C++
|
|
|
|
|
I agree with you that the coding process needs to be improved. I inherited this application when I took a new job. The app is updated/enhanced about once or twice a month. Currently, these changes are taking longer to implement because the code is performing the same functionality in several different places.
My motiviation for moving the application to .Net is to redesign/rewrite the application (it is not a large app, it should only take 2 months to rewrite). My problem is I can't go to the business and say the current application is a mess and needs to be rewritten, but I can say VB6 is no longer supported by Microsoft. But I need to provide more reasons for upgrading.
Thanks. Any ideas?
|
|
|
|
|
mr_12345 wrote: My problem is I can't go to the business and say the current application is a mess and needs to be rewritten
Why not ? You didn't write it. Point out that the app will in the long term be more cost effective for them if it's rewritten so that it's easier to extend and maintain. Point out the cost benefits of moving to a modern framework with support for lots of stuff that's not there in VB6. Point out the benefits of being able to run VB.NET code through VSTO and SQL Server 2005 stored procs ( if you use a database ). Unless your boss wrote it, if you talk in terms of cost benefit, you're talking their language.
Christian Graus - Microsoft MVP - C++
|
|
|
|
|
Because I work for company A who wrote the application for company B. Now A is telling B that we need to rewrite/redesign the application?
|
|
|
|
|
Don't try to con your employers into letting you re-write it in .NET by telling them VB6 is no longer supported; tell them the truth and inform them of the costs, benefits, and dangers then let them make the decision. Another aspect is that you need not port the whole application at once. You could test the waters by making a new component or recoding an existing one using .NET and use interop. In my opinion this is the best approach.
Steve
|
|
|
|
|
VB6 IS no longer supported. I'm a moderator on the MSDN forums, and we lock VB6 questions and tell them to find help elsewhere.
Christian Graus - Microsoft MVP - C++
|
|
|
|
|
My intention was NOT to suggest that VB6 was supported, it was in response the following comment from the OP:
"My motiviation for moving the application to .Net is to redesign/rewrite the application (it is not a large app, it should only take 2 months to rewrite). My problem is I can't go to the business and say the current application is a mess and needs to be rewritten, but I can say VB6 is no longer supported by Microsoft. But I need to provide more reasons for upgrading."
I have underlined bits to make my point clearer. Hopefully what I meant when I said, "don't try to con your employer" is now a bit clearer.
Steve
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
