Re: VFP9SP1 Error 1705 access denied when running INDEX on MyDateFld tag MyDateFld
INDEX ON Transdate TAG Transdate Do you get the same error with INDEX ON DTOS(Transdate) TAG Transdate Gérard. ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: VFP9SP1 Error 1705 access denied when running INDEX on MyDateFld tag MyDateFld
I've seen some intermittent problems solved by putting a SELECT csrTrans between the SELECT and the INDEX ON statement. In addition to that, you could put an ORDER BY Transdate in the SELECT. If they're using this table for viewing records, (and not SEEKing or LOCATEing) then the result may be the same as creating the index. In addition to that, and I'm not sure what version of VFP you're using, but you could wrap the INDEX with a TRY .. CATCH. Just my $0.02. Believe it or not, I'm most hopeful about just putting the SELECT csrTrans between the statements. It seems to force VFP to straighten out the work areas for me. -Kevin CULLY Technologies, LLC MB Software Solutions General Account wrote: SELE *,00.00 AS AmtUsed; FROM TRANSACT; WHERE inqnum = nInq; AND Amount != 0; INTO DBF (Temppath + csrTrans.dbf) INDEX ON Transdate TAG Transdate ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: VFP9SP1 Error 1705 access denied when running INDEX on MyDateFld tag MyDateFld
Ken Dibble wrote: I've checked the values in the Transdate column in that table: 1 record with a crazy date back in the year 0120, 2 records where it was 0220, 1 from 1901 and the rest appear to be normal. And these goofy records aren't even the ones in the query result. I don't know the answer to your problem but the above got my attention. I've got a handful of records in a table of about 30,000 service dates where the year is something impossible like that: 0007, 0008. I don't see how this can happen. SET CENTURY is ON, and the textbox where the dates are entered is formatted for dates, so if a user entered a date like 10/1/0007 s/he'd get a VFP Invalid Date error and wouldn't be able to do anything until s/he fixed it, let alone saving the data. Also, my date validation code won't allow service dates to be entered that are more than a couple years old. Again, this has only happened with about a half dozen records out of around 30,000, so it has to be something extremely random. I wonder if you have any thoughts on how such years can get entered? In my case, these dates could have been entered long ago, as this app is very old (but still kicks asslol!). Perhaps it was before they put any constraints/controls into play to force good dates. ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: VFP9SP1 Error 1705 access denied when running INDEX on MyDateFld tag MyDateFld
Kevin Cully wrote: I've seen some intermittent problems solved by putting a SELECT csrTrans between the SELECT and the INDEX ON statement. In addition to that, you could put an ORDER BY Transdate in the SELECT. If they're using this table for viewing records, (and not SEEKing or LOCATEing) then the result may be the same as creating the index. In addition to that, and I'm not sure what version of VFP you're using, but you could wrap the INDEX with a TRY .. CATCH. Just my $0.02. Believe it or not, I'm most hopeful about just putting the SELECT csrTrans between the statements. It seems to force VFP to straighten out the work areas for me. -Kevin CULLY Technologies, LLC Yep...I follow the same practice as you. Whenever I'm in areas of code being checked out and modified, I don't mind adding these kinds of things so that they're taken care of in the next release. I agree with your approach for being proactive in the future...just like I always use the IN clause when possible (e.g., REPLACE LastName with Cully in MyTable). ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: VFP9SP1 Error 1705 access denied when running INDEX on MyDateFld tag MyDateFld
Gérard Lochon wrote: INDEX ON Transdate TAG Transdate Do you get the same error with INDEX ON DTOS(Transdate) TAG Transdate Hi Gérard, It's a solution already deployed in the field, and I can't ship them an updated EXE to test this. When I get their data, it doesn't fail for me at all. Sounds definitely like the A/V getting in the way. I connected to the client's PC (...thank God for the creators of LogMeIn !) and configured her PC to ignore our VFP folders, so that should hopefully take care of it. So far, so good. ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: VFP9SP1 Error 1705 access denied when running INDEX on MyDateFld tag MyDateFld
Michael Madigan wrote: You're right, it should have nothing to do with locking on a local disk, but know knows? I would also turn off the local disk write caching to see if that makes a difference. Did that already...problem still crept up. It could also be a phony error that's completely unrelated to the error you are getting. I hate intermittent errors. I agree!! ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
RE: VFP9SP1 Error 1705 access denied when running INDEX on MyDateFld tag MyDateFld
Anti-Virus gets a lock. -Original Message- From: MB Software Solutions General Account Sent: Tuesday, September 30, 2008 6:13 PM We've got a client in the field who runs a report and it creates an oddball error, one that no one else is apparently gettingand the best part---it doesn't always happen, and it happens on multiple machines if I heard her right. It's legacy code from eons ago so it's not like we just introduced a bug recently with new code in that area of the program. The code is as follows, copied exactly as it is in the source: SELE *,00.00 AS AmtUsed; FROM TRANSACT; WHERE inqnum = nInq; AND Amount != 0; INTO DBF (Temppath + csrTrans.dbf) INDEX ON Transdate TAG Transdate The Temppath variable holds a LOCAL location that's generated by the app (e.g., C:\Symplcty\SymPrefs\TempSym\_2GN0NJO2Z). I've checked the values in the Transdate column in that table: 1 record with a crazy date back in the year 0120, 2 records where it was 0220, 1 from 1901 and the rest appear to be normal. And these goofy records aren't even the ones in the query result. If I were rewriting the code today, I'd change it to use a local CURSOR output, but apparently the original developers either didn't have CURSORS available to them or didn't understand how to use them OR just preferred to have local DBFs so they could check data as they debugged from other Fox windows. (I knew a legacy guy who practiced the latter...may he RIP.) Can anyone give a reason as to why the INDEX ON Transdate TAG Transdate line would throw an Error 1705 File access is denied on the CDX file? It's worthy of noting too that my colleague and I went to the folder to see the files, and the DBF and FPT were there, but NO CDX was present. WEIRD!!! Any advice appreciated...thanks --Michael ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
RE: VFP9SP1 Error 1705 access denied when running INDEX on MyDateFld tag MyDateFld
IT might also be opportunistic locking causing a problem. Just for laughs, turn off opportunistic locking on that share. --- On Tue, 9/30/08, Tracy Pearson [EMAIL PROTECTED] wrote: From: Tracy Pearson [EMAIL PROTECTED] Subject: RE: VFP9SP1 Error 1705 access denied when running INDEX on MyDateFld tag MyDateFld To: profox@leafe.com Date: Tuesday, September 30, 2008, 6:02 PM Anti-Virus gets a lock. -Original Message- From: MB Software Solutions General Account Sent: Tuesday, September 30, 2008 6:13 PM We've got a client in the field who runs a report and it creates an oddball error, one that no one else is apparently gettingand the best part---it doesn't always happen, and it happens on multiple machines if I heard her right. It's legacy code from eons ago so it's not like we just introduced a bug recently with new code in that area of the program. The code is as follows, copied exactly as it is in the source: SELE *,00.00 AS AmtUsed; FROM TRANSACT; WHERE inqnum = nInq; AND Amount != 0; INTO DBF (Temppath + csrTrans.dbf) INDEX ON Transdate TAG Transdate The Temppath variable holds a LOCAL location that's generated by the app (e.g., C:\Symplcty\SymPrefs\TempSym\_2GN0NJO2Z). I've checked the values in the Transdate column in that table: 1 record with a crazy date back in the year 0120, 2 records where it was 0220, 1 from 1901 and the rest appear to be normal. And these goofy records aren't even the ones in the query result. If I were rewriting the code today, I'd change it to use a local CURSOR output, but apparently the original developers either didn't have CURSORS available to them or didn't understand how to use them OR just preferred to have local DBFs so they could check data as they debugged from other Fox windows. (I knew a legacy guy who practiced the latter...may he RIP.) Can anyone give a reason as to why the INDEX ON Transdate TAG Transdate line would throw an Error 1705 File access is denied on the CDX file? It's worthy of noting too that my colleague and I went to the folder to see the files, and the DBF and FPT were there, but NO CDX was present. WEIRD!!! Any advice appreciated...thanks --Michael ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious. ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: VFP9SP1 Error 1705 access denied when running INDEX on MyDateFld tag MyDateFld
Michael Madigan wrote: IT might also be opportunistic locking causing a problem. Just for laughs, turn off opportunistic locking on that share. It's totally LOCAL, not on the LAN, so that doesn't seem likely. Isn't that suggestion for LAN files only? ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: VFP9SP1 Error 1705 access denied when running INDEX on MyDateFld tag MyDateFld
You're right, it should have nothing to do with locking on a local disk, but know knows? I would also turn off the local disk write caching to see if that makes a difference. It could also be a phony error that's completely unrelated to the error you are getting. I hate intermittent errors. --- On Tue, 9/30/08, MB Software Solutions General Account [EMAIL PROTECTED] wrote: From: MB Software Solutions General Account [EMAIL PROTECTED] Subject: Re: VFP9SP1 Error 1705 access denied when running INDEX on MyDateFld tag MyDateFld To: ProFox Email List profox@leafe.com Date: Tuesday, September 30, 2008, 6:42 PM Michael Madigan wrote: IT might also be opportunistic locking causing a problem. Just for laughs, turn off opportunistic locking on that share. It's totally LOCAL, not on the LAN, so that doesn't seem likely. Isn't that suggestion for LAN files only? ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious. ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: VFP9SP1 Error 1705 access denied when running INDEX on MyDateFld tag MyDateFld
I've checked the values in the Transdate column in that table: 1 record with a crazy date back in the year 0120, 2 records where it was 0220, 1 from 1901 and the rest appear to be normal. And these goofy records aren't even the ones in the query result. I don't know the answer to your problem but the above got my attention. I've got a handful of records in a table of about 30,000 service dates where the year is something impossible like that: 0007, 0008. I don't see how this can happen. SET CENTURY is ON, and the textbox where the dates are entered is formatted for dates, so if a user entered a date like 10/1/0007 s/he'd get a VFP Invalid Date error and wouldn't be able to do anything until s/he fixed it, let alone saving the data. Also, my date validation code won't allow service dates to be entered that are more than a couple years old. Again, this has only happened with about a half dozen records out of around 30,000, so it has to be something extremely random. I wonder if you have any thoughts on how such years can get entered? Ken Dibble www.stic-cil.org ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
