Search results for query: *

I finally found it (with the help of someone else) that to get rid of the 5 decimal places you have to define your fields in the table to be exported as DECIMAL. Then you can define the number of digits and decimal places for each field and when exporting to dbase (5.0) the fields in the .dbf...

I finally found it (with the help of someone else) that to get rid of the 5 decimal places you have to define your fields in the table to be exported as DECIMAL. Then you can define the number of digits and decimal places for each field and when exporting to dbase (5.0) the fields in the .dbf...

@PaulBricker: Of course I could export the tables to somethinge else but dbase but this would require some more step of conversation for the user to finally generate the needed dbase files "resp." is an abbreviation for "respectively" @dhulbert: The target application is a Lotus Notes...

>How are these values originally generated? I have tables with fields defined as LongInteger resp. Double. They are set up to have fixed decimal places (0 resp. 2). The data is added to these tables programmatically by means of execution of stored insert queries basing on data from other...

Hi, Tim if it were not the dbase format but Excel, CSV, Word or whatever I would not hesitate to manipulate the data after export using VBA or whatever, but manipulating dBase files is somewhat tricky and might make them unreadable for the following application. And since the export is part of...

It would be really helpful to know something about your system: - OS/version - Access version - type of used access database (or is it with any db?) - since when does this happen and what changes where made to your system before this behaviour started ???

When I convert the fields to text (using a query) and then export the result of this query into a dbase file, every text field has a length of 254 characters and no decimal places at all. Also it is of type "C" (character) which is incompatible with the application which imports the dbase files...

>Just some random thoughts. Thank you for thinking ;-) >If you define the field as currency, then you should >only get 2 decimal places. >The caveat is you get placeholders for the thousands >digit, and you get the $ sign. You might be able >to strip those out in dbase. The target...

When invoking the Windows login screen the current user would in fact be logged of and the new user be logged in. Since all users use the same login - what would be changed then!? On the other side if it were possible for every application to present the user a "windows login screen" and catch...

Don´t waste your time. There is no programmatic solution for dumb computers to tell the name parts apart. Just imagine that if there was only one field for names, everybody could type in whatever they want: Tommy Aunt Mary John Doe J. R. Ewing John Foster Dulles Kennedy, John F...

But what if there are names like John Paul Jefferson Smith III jr. What would you consider to be the first and the last name and what about other name parts like suffixes?

Exporting tables from Access to dbase files causes 5 decimal places for all number fields. This is unwanted since the other application which imports the dbase files expects number fields with e.g. 0 or 2 decimal places. Does anybody know how to tell Access the number of decimal places to use...

BillPSUs answers are not very helpful for me... Have you, ddelk, or anybody else found a solution for this problem? I am facing the same problem and have no clue how to solve it - and cannot export to CSV or sth. else, or change the format of the dBase table since there is a 3rd party...