numeric instead of bigint & create/delete tbl

I am just at the beginning of a new SQL-db and versus my bad habits earlier, where I didn't care for the right data-type, I would put my full focus first on my tables with the correct datatypes. I now have some fields where I store some balance-sheetnumerbs which are often in the high billions and therefore I chosen bigint but found out as I run Access2013 in frontend, latter can't handle this format. As no decimal is needid in these fields, shall I go for numeric instead as mentioned in the blog?
http://sqlblog.com/blogs/aaron_bertrand/archive/2009/10/12/bad-habits-to-kick-using-the-wrong-data-type.aspx

and secondly, I used to store some intermediate results out of queries in tables which I fill with data for more calculations and when the user closes the form, I delete the data in the table but not the table itself. Is this a reasonable way as I assume an empty table doesn't take a lot of space or do you recommend to DELETE/CREATE table each time and if yes, how to handle the possibly some users do the same query at the same time? I handled this by adding a username-field in the table, but if I go for CREATE/DELETE, it can happen that a user deletes the table?!
KongtaAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Walter RitzelSenior Software EngineerCommented:
1) Numeric seems to be an alternative.
2) About the tables piece, if you are using SQL Server as you mention and just your front end is Access, why dont you use temporary tables for the intermediate calculations and such? Depending on how you are doing it, temporary tables could be a good alternative.
KongtaAuthor Commented:
right now, I created empty tbls which I fill with the results of the queries and if the output is not needed anymore I delete the content and leave the skillet, all done in SQL. It works okay for me but I always see that people create/delete tables instead of leaving the skillet. I am wondering if I do wrong on indexing-aspects or whatever, space can't be the issue as the tbl are mostly empty. But if people use create/delete, how you handle the problem that two users might do the same at same time? Do you mark the tbl-name including a user-ID?
KongtaAuthor Commented:
do you see real as an alternative as well? just found out that numeric is not accepted in Access as well, get ODBC-error
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Walter RitzelSenior Software EngineerCommented:
Kongta, I'm not sure I'm following your design: you mention you have created all in SQL, but it is not clear if this was on access or SQL Server. If it is on Access, maybe the way you are going to deal with that will be like you mentioned (create tables with userid in the name). But if those tables are only for the purpose of calculating certain things to speed up, if you do on SQL Server, this could be achieved like I've mentioned (temporary tables) and that would be session bound, so would be naturally separated by user.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Walter RitzelSenior Software EngineerCommented:
Real is acceptable, too.
KongtaAuthor Commented:
yes, all calculations are done in SQL, therefore I think I give the temp.tables a try. have many thanks. best rgds, Kongta
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.