Search results for query: *

Update: I just did some more work on this and noticed that if I PRINT the graph, it prints the correct data, but is DISPLAYING incorrectly. This means that what I'm seeing on the screen, and what comes out of the printer when I hit the print button are DIFFERENT. Makes it even more mind...

I am having a problem diplaying graphs in Microsoft Access. I currently have a Form that updates a table using SQL Insert Statements. The table has 4 fields in it, and will update with anywhere between 100 and 1000 records, depending. After the table is updated from date range and line #...

Well, the answer is I did not find an answer. After spending a lot of time on the phone with Microsoft, they could not help me. My organization migrated to Windows 2000 where the error has not been present (nor was it present in WinNT machines). I think it has something to do with memory...

Two methods of doing this. Not sure about the first one working though. Use the between statement formatted with # signs, like #08/25/79# . Second option, and this is how I do it on a program I've written. Instead of storing 08/25/79 Date formats into your text field, store it 19790825...

I've started getting a similar error in an app I coded in Access 97 and was recently converted to 2k. I'll try and post a fix when I get one (It's a critical app, and has to be fixed soon).