We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Solved
Access 2007 Make Table query number format
Posted on 2011-03-09
Hi, I am creating a make-table query with a number field. I'd like the number field with 4 decimal places in the output table. How do I do that? Thanks.
[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
2
2
- +2
8 Comments
In design view of a Make Table Query use a Format function of the column you want to format:
E.g. Account1:Format([Account],
Sincerely,
Ed
E.g. Account1:Format([Account],
Sincerely,
Ed
I don't think you can do this within the make-table query.
Mindsuperb's answer will create a text field, not a number field, although the results for the current data will show with 4 dp in that text field.
Mindsuperb's answer will create a text field, not a number field, although the results for the current data will show with 4 dp in that text field.
You could use a conversion function in the SQL to make sure that you have a field that is the correct datatype.
SELECT CCur(MyNumberColumn) INTO MyTable
The problem that you have is one of formatting, and that will have to be set using either DDL to alter the column format (tough-ish in Access), or using ADOX (ok-ish), or by hand.
A solution that is used all the time in the data warehousing world is to use more than one layer of tables. Use the make table code to pull the data in (or better use a "kill and fill" truncate and load), but then transfer it to a staging table that's in the correct format, validate it, then pull it in to the main database.
SELECT CCur(MyNumberColumn) INTO MyTable
The problem that you have is one of formatting, and that will have to be set using either DDL to alter the column format (tough-ish in Access), or using ADOX (ok-ish), or by hand.
A solution that is used all the time in the data warehousing world is to use more than one layer of tables. Use the make table code to pull the data in (or better use a "kill and fill" truncate and load), but then transfer it to a staging table that's in the correct format, validate it, then pull it in to the main database.
I agree that the poster is not getting a workable solution.
That is because, as I said in my response, it can't be done in the way they are asking.
Andrew Weir gave an approach that is can be used to carry out the poster's requirements.
The table must be defined in advance and an append query used, or the table must be modified in code to set the number of decimal places.
Another code example.
CurrentDb.TableDefs("<tbln
That is because, as I said in my response, it can't be done in the way they are asking.
Andrew Weir gave an approach that is can be used to carry out the poster's requirements.
The table must be defined in advance and an append query used, or the table must be modified in code to set the number of decimal places.
Another code example.
CurrentDb.TableDefs("<tbln
Thanks Peter, that's exactly right.
JCJG, there is no magic way to do this, it's going to take several steps to make sure that it works as you want it to. I've had to build solutions for problems like this many times, and it's exactly as Peter and I have described.
JCJG, there is no magic way to do this, it's going to take several steps to make sure that it works as you want it to. I've had to build solutions for problems like this many times, and it's exactly as Peter and I have described.
Featured Post
Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.
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
If you find yourself in this situation “I have used SELECT DISTINCT but I’m getting duplicates” then I'm sorry to say you are using the wrong SQL technique as it only does one thing which is: produces whole rows that are unique. If the results you a…
I'm trying, I really am. But I've seen so many wrong approaches involving date(time) boundaries I despair about my inability to explain it. I've seen quite a few recently that define a non-leap year as 364 days, or 366 days and the list goes on.
…
We’ve all felt that sense of false security before—locking down external access to a database or component and feeling like we’ve done all we need to do to secure company data.
But that feeling is fleeting. Attacks these days can happen in many w…
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…
Suggested Courses
Course of the Month12 days, 3 hours left to enroll
636 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.