I am trying to insert a date into sql Server 2000.
I am using the INSERT...VALUES in an SQL statement with VB, But I keep getting the message that SQL cannot convert char to smalldate.
This is hacking me off!!
This is an example of code that does not work -
INSERT INTO someTable(cName, cDate)...
I have an Access 2000 database which also has links into Sage. The application works with no faults under the full version of Access but when it is packaged & deployed in runtime it periodically ceases in two places. The coding behind the two forms is fine, the code simply checks that certain...
okay, what about this one then....
I have a data entry form on which one of the fields is a date defaulting to todays date, ie date(). The form adds the appropriate record fine on my PC but when the application is packaged into runtime & loaded onto a target PC the date converts itself to...
Calling all 'clever dicks' out there...
I have a front end which is linked to the back end via the path set in 'linked table manager'.
Anyone know of a procedure to allow the end user (who will be using an MDE version of the front end) change the path of the database as and when required...
I'd heard that it is bad practise not to enforce referential integrity when adding relationships to tables. If this is so how do you get around the following scenario without setting up a dummy record in the Suppliers table??
eg You may have orders that require a record in a supplier's table...
Can anyone help with some code that I can store in a module for use by all forms in my database that require Move First & Move Last navigation buttons. Basically when the user clicks on the Move First or Move Last button when they are already at the first or last record I want to be able to...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.