I need some input on what to use for a field that contains a range of IP addresses, and have it sort numerically by octet. I currently have that field assigned as text, but were not happy with the sort order. I've played a little with the number format type, but still did not get the correct sort order. Any suggestions would be appreciated. Thanks
I am exporting data from access 2007 to Excel 2007 using VBA code. I have a whole number, which I want displayed as whole number. But after the export, the number is using the 1000's seperator in Excel. So for example if my original number in access table is 12000, it is showing up as 12,000 in the excel file.It has something to do with the NumberFormat property. I have tried doing this but doesn't work.
I have Set a Field as a Long Integer (and have tried Standard) Number with two decimal places. I enter data and it always displays as .00 and not the correct figures. Any clues anybody?
I have a query that looks like this, datediff("d",[end_date],[start_date])/30 it's working perfect, but it's give me a decimal number, how can I formate it to get rid of the decimals, if I put "m" instead of the "d" than this number won't be accurate, can someone help? thanks.
I am trying to enter a field with total hours for the day. I have set as "General number, 2 Decimal places. When I input the number [18.25] which means 18 and 1/4 hours..... The field will only display 18.00, I can not get it to show the .25.... I think the field is rounding off the number and if it is how do I get it to stop... I need this field to give me a sum in a report.... Need some help....
I was about to post a question yesterday, but I found a solution myself and would like to share it. When a new column is computed in the query, there is no way to prescribe the data format of the computed column (=field =variable). It is done automatically by access and it can go wrong. I tried to use Format() function but it changes the look but does not change the type of the column. So what you have to do is to wrap your expression in a data convertion function. I used CDBL() as a wrapper for my expression.
I consider it as a bug of Access because in my situation I had a swich() function that took only numeric fields and produced only number but the data type of the column was set to TEXT. I noticed it in the pivot table later on , when I could only use Count() as aggregate function.
Good luck! and take care of data conversion by yourself, do not let it go automatically!
P.S. If anyone knows a better way to prevent such conversion errors, be my guest!!!
I have been confronted with a strange fenomenon in comboboxes.
I'm working with access2000. I put a simple combobox in a form. The row source of the combobox is a table and the first field of this table is a number. The bound column is 1. When I select a record in the combobox, that number appears, it all seems to work.
However, when I reference the content of the combobox via a query, I receive strange characters. When I ask for the ASCII value of that character, it is mostly 49 (1) or 50(2). When I set the column width to zero, the references just work fine. When I change the format to text, everything works fine.
Can someone explain why this is happening?
I include a simple database to show what is happening. Look at the queries.
Hello, I have a text file I'm querying that stores a field as a text. ComponentID:0000000242
I'm inserting this data into a table that stores this value as a number. Thus truncating the leading zeros. ComponentID:242
I would like to create a query on the table using an InnerJoin on the text file column:ComponentID:0000000242 and the table column:ComponentID:242 as the unique identifier. Doing this join gives a case error because of the different data types.
Can format ComponentID using a query so it reads from my table as 0000000242 and do an InnerJoin to the text file. In vb String= Format(242, "0000000000") But I'm finding it difficult to get the query to format this correctly.
Unfortunately, i'm unable to change the column data type in the table structure and am looking for a work around. Is this even possible? Any ideas?
I have imported in an excel table into access. It has a lot of numbers that have many digits after the decimal place. I want to cut this down since they are prices to just 2 decimal places.
Problem is that access imports the fields as Text fields. when i go to change the columns that i want as numbers it looses the information after the decimal place for example 1.1156834 when i click Number (long integer) and standard format it is converted to 1.00 loosing everything. This is getting really really fustrating now.
When i import there is a drop down list but it is disabled where i can change the column property (number, text etc) so cant do anything about it.
I have imported in an excel table into access. It has a lot of numbers that have many digits after the decimal place. I want to cut this down since they are prices to just 2 decimal places.
Problem is that access imports the fields as Text fields. when i go to change the columns that i want as numbers it looses the information after the decimal place for example 1.1156834 when i click Number (long integer) and standard format it is converted to 1.00 loosing everything. This is getting really really fustrating now.
When i import there is a drop down list but it is disabled where i can change the column property (number, text etc) so cant do anything about it.
I have a query that I want the Now() function in the year only format and in an expression combine with the auto number one extra field to get the following:date YYYY-------Autonumber---------color----------exp1: ---2007--------------23--------------green-------2007-23-greenThanks for the help
The 1st/2nd Jan of this year were treated by most people as still being week 53 of 2004, and week commencing 3rd January being week 1 of 2005. In VB I have a formula to do this:
I need the auto number to be in specified format as ASI-23-0001. So I added the format "ASI-23-"0000 in the formats and I got it succesfully.The fueld name is "Part Number"
I have added the Part Number field to a form as combo and I was able to list the values in the drop down combo.
I wanted to use Dlookup command in the program to auto fill the next field in the form say "Description".
I am using the following code Me.Text30 = DLookup("[Description]", "item_master", "[Part Number] = Form![Combo36]")
But now the data in the combo is treated as text because of the prefix "ASI-23" and I get data type mismatch error.
Is there a way I can format AutoNumber for a primary key, for example, have the first ID start as C001 then for the next entry Access will automatically go to C002, and so on and so forth?
I have the following VBA code to search for a string
Code: 'Search by Phone Private Sub CmdSearchPhones_Click() Me.Refresh strSQL = "SELECT Tbl_Contacts.ContactID, Tbl_Contacts.FName, Tbl_Contacts.LName, Tbl_Contacts.Address, Tbl_Contacts.City, Tbl_Contacts.State, Tbl_Contacts.Zip, Tbl_Contacts.HomePhone, Tbl_Contacts.WorkPhone,
[Code] .....
My issue is that this works 50/50, because phone numbers on the database are NOW being stored in this format (000) 000-0000 and previous DB phone numbers got stored as 0000000000. The above code finds previous DB phone numbers (even if we dont enter all 10 digits) without a problem but has issues with new phone numbers stored in the new format UNLESS I specify the search with (000) 000-0000 (but we want to be able to search without adding that and without typing all 10 digits - in case we forget part of the number we are looking for)
How can I tell my query to find both formats, with the (000) 000-0000 AND 0000000000 ....
I have a mail merge from Access into Word that works great except for a baffling problem with phone number formatting. Instead of (987) 654-3210, on certain records the merge produces 9876543210. I cannot identify a pattern to explain it, but it is not random. Certain records consistently leave the format behind on the phone number, some on the fax number, and some on both. This problem is affecting about 1/3 of the contact records. I have the Input Mask on Phone and Fax in the table set to !(999") "000-0000;0;_. Is anyone familiar with this problem?
I have an inherited database with years worth of julian dates stored as numbers (e.g. days 1-366 for a leap year). I also have some fields stored as short dates. I would like to run a series of parameterized queries on this data, some using the short data and some using the "julian dates" that are actually just numbers. I have the user enter the start and end date in short date format and would like that to be converted and held in an unbound field as a number value. So far I can get the date to appear as a "julian date" (e.g. 1/1/08 appears as 1, obviously the underlying data is still 1/1/08) How do I take that 1 and convert it to number value "1"? Thanks in advance.
I am importing data to a program that requires the life of an item. This is in months such as 241 months. The valid format for this program is YYMM. 241 = 2001 or 20 years 01 month.
Another example: 16 months should read 0104 or one year 4 months.
Any idea how to convert this to yymm format based on the number of months?
I upgraded my system to Windows 8 and Office 2013, and it's now 64 bit instead of 32 bit as before. Also note that I'm still using Access 2010 as before.So the following problem now arise in this new config that was not there before.
When you do a calculation like '332.16 - 1', the answer is now 331,16, instead of 331.16. Note the point are now replaces with a comma.
Might sound trivial, but everywhere in my code where is have a dynamic SQL like:
INSERT INTO Tasks (TaskID, MyNumber) VALUES ("Tsk123", 331.16), but now it is: INSERT INTO Tasks (TaskID, MyNumber) VALUES ("Tsk123", 331,16), so it is seen as an extra value and the statement fails.
So, yes I can fix this one statement, but I have multiple occurrences of this throughout my app. How do I fix this?
And changing something in my Control Panel - Regional Settings would not be the answer, as on all the client PC's it might be different.