[RESOLVED] It has been working fine for 3 months but ...
Hi,
I have been using this application for 3 months. It was working fine till yesterday. But now it is not working. Showing runtime error '13' when I am trying to save the data (and it highlights the code which is shown in bold in the following code).
Has anyone changed the datatype of InvoiceDate field in the database? And have you checked what is there in txtInvoiceDate.Text?
I am the one who is using this computer. I have not changed anything in this project. Just using to enter some data. What I have done is, installed some games on this computer, some of those causing error and not working. I have 4 tables in this database which has date fields in it. And all those causing the same error when saving the data.
The following jpg file has some details. I have not changed any code recently.
Regards,
Seema_S
I am getting the following error (jpg) frequently since yesterday when I am trying to play games. Is this the error causing the application getting that error?
I don't think this will be the reason why you are getting an error in your VB App.
Did you try what I suggested?
Hi,
My all applications are having problem when trying to save them. Even some applications which doesn't have date value also saving fields as blank. I have re-installed the visual basic 6.0, but the problem is same.
Regards,
Seema_S
Last edited by seema_s; Jul 12th, 2006 at 03:39 AM.
Well I am clueless as to what will cause this problem. Probably you installed something recently that screwed Windows. An Update or something similar to this.
Use [code] source code here[/code] tags when you post source code.
Well I am clueless as to what will cause this problem. Probably you installed something recently that screwed Windows. An Update or something similar to this.
Hi,
Now it is working properly. The problem was with regional settings (date format). But still I don't know why those applicantion did not work which has only one txtbox (txtReminder) with string property.
Thanks.
Seema_S
Last edited by seema_s; Jul 12th, 2006 at 05:50 AM.
Re: [RESOLVED] It has been working fine for 3 months but ...
dd/mm/yyyy is a date format that MS SQL does not like - was this ACCESS or MS SQL? I believe ACCESS also does not like that format.
CDate() follows regional settings - so you are at risk of problems with CDate().
I believe that the FORMAT() function can be told to force MM/DD/YYYY regardless of regional settings.
I was burned by regional settings in our high school attendance application when the spanish teacher selected commas as decimal points instead of periods...
*** Read the sticky in the DB forum about how to get your question answered quickly!! ***
Please remember to rate posts! Rate any post you find helpful - even in old threads! Use the link to the left - "Rate this Post".