Visual Basic - BindingNavigator is imploding my studio

Ok, so, it sounds like you're not inserting the studentID. I can't remember access database. It's been years, but generally you either set the unique ID (which I assume this column is) to auto increment, or you have to manually populate it.

Is your studentID set to autoincrement or do you manually set it?
 
Grieta Thanburg said:
Ok, so, it sounds like you're not inserting the studentID. I can't remember access database. It's been years, but generally you either set the unique ID (which I assume this column is) to auto increment, or you have to manually populate it.

Is your studentID set to autoincrement or do you manually set it?
Click to expand...
Manually, something like "DA-200069" for example.
 
Grieta Thanburg said:
Ok, so, it sounds like you're not inserting the studentID. I can't remember access database. It's been years, but generally you either set the unique ID (which I assume this column is) to auto increment, or you have to manually populate it.

Is your studentID set to autoincrement or do you manually set it?
Click to expand...

Yeah, go into VB debug mode and step through the code. See what data the frontend is trying to send to the database, if its trying to send a null to the column then there's some kind of binding issue on the field.


It reminds me of ages ago when I worked for this guy who liked to think of himself as a master of IT, he'd take time off every now and then to go lecture at a university to the first years. Of course that also allowed him to bring them back and use them as cheap labour while they were interning.

At the time we were still using C/C++ and just getting into C#/JAVA, but they were required to use Delphi which is a fine language, but like the above if you don't know what you're doing it's very easy to mess up. They spent 3 months or so building us a tool that would interact with some low level hardware (I wrote the C interface to speak directly to it and they just called the methods). Mostly the thing worked, but it had so many little binding and other issues. After they left it fell to me and I struggled with it for probably two weeks, but not being versed in Delphi I eventually gave up and just re-wrote the whole thing in a day using C.
 
Grieta Thanburg said:
I mean, technically, a language is a language. It's about understanding the fundamentals.
Click to expand...
Vb does a lot of handholding and did a lot of lazy declarations. At that level, they should be being forced to understand what is happening under the hood so languages like java, c/c++ etc as fundamentals.

You could do c# vs vb for a more modern twist but c# now also does a lot of obfuscation.
 
Kosmik said:
Vb does a lot of handholding and did a lot of lazy declarations. At that level, they should be being forced to understand what is happening under the hood so languages like java, c/c++ etc as fundamentals.

You could do c# vs vb for a more modern twist but c# now also does a lot of obfuscation.
Click to expand...
Vb.net and C# only differs in syntax. For the rest, the .Net framework that does the work is exactly the same. I program in both and for 98% of the code you can do a direct translation from Vb.net to C# and vice versa.

Java, C and C++ are the best but far too time consuming for use in a modern development shop that has to compete with other development shops on price. Also to say young developers should start with the likes of Java and C, is the same as telling programmers 35 years ago that they should not program in Visual Basic and Pascal but rather in Assembly.
 
Stonemason said:
Vb.net and C# only differs in syntax. For the rest, the .Net framework that does the work is exactly the same. I program in both and for 98% of the code you can do a direct translation from Vb.net to C# and vice versa.

Java, C and C++ are the best but far too time consuming for use in a modern development shop that has to compete with other development shops on price. Also to say young developers should start with the likes of Java and C, is the same as telling programmers 35 years ago that they should not program in Visual Basic and Pascal but rather in Assembly.
Click to expand...
cough cough, we did exactly that :ROFL:

And the main reason why I say java, c++ etc is to learn things like garbage collection, heaps and pointers or at least the concepts thereof.

We did also do assembly , PICs if I recall.

Assembly, c , c++ , html and old zenworks for learning about domains/ads etc etc etc.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X