Solved

Y2K Issue w/ VB 6 & Access 97

Posted on 1998-11-19
1
183 Views
Last Modified: 2013-12-25
I have created a VB 6.0 app using the Access 8.0 Object Library to handle data transactions with an Access 97 database.  One of the transactions involves the TransferDatabase method, where I import a dBaseIV file into the Access 97 database.  In the dBaseIV file, the date fields are stored with the century indicator in the form, mm/dd/yyyy.  However, after I execute the TransferDatabase method, the dates are displayed in the new Access 97 table as mm/dd/yy.  

Question 1:  Are the dates merely displayed as mm/dd/yy but stored as mm/dd/yyyy?
Question 2:  Does Access 97 use windowing to determine the century indicator?  (i.e., if I append these records to another table where the format of the date fields is mm/dd/yyyy, will Access window to determine which century the year is in?)

Question 3:  How can I transfer the dBaseIV file so that the dates are initially stored as mm/dd/yyyy?

I appreciate your time and attention to this matter.
0
Comment
Question by:dfhaines
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 

Accepted Solution

by:
Coates earned 200 total points
ID: 1497726
Ive found sometimes that access follows the regional settings of the PC, no matter what formatting is applied to them.
I think they may still be stored as dd/mm/yyyy, put the regional settings may cause them to be displayed otherwise.
Give this a try
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When trying to find the cause of a problem in VBA or VB6 it's often valuable to know what procedures were executed prior to the error. You can use the Call Stack for that but it is often inadequate because it may show procedures you aren't intereste…
Have you ever wanted to restrict the users input in a textbox to numbers, and while doing that make sure that they can't 'cheat' by pasting in non-numeric text? Of course you can do that with code you write yourself but it's tedious and error-prone …
Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…
Show developers how to use a criteria form to limit the data that appears on an Access report. It is a common requirement that users can specify the criteria for a report at runtime. The easiest way to accomplish this is using a criteria form that a…

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question