The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
MS Access Question
Deebaser
on my way to work in a suit and a tieAhhhh...come on fucking guyRegistered User regular
on my way to work in a suit and a tieAhhhh...come on fucking guyRegistered User regular
Im trying to simplify my life and throw a long series of boring queries into an mdb file, but I'm hitting a roadblock with one of my joins.
I need to create a left join invoice_num from my dataset on INVOICE on our accounting database.
invoice_num is stored 100001
INVOICE is stored L100001-000
here's the code I've been using to date to do a quicky equi-join. Should I just temptable this bitch?
i.INVOICE like ("%" + CONVERT(varchar(20), lol.invoice_num) + "%")
I need to create a left join invoice_num from my dataset on INVOICE on our accounting database.
invoice_num is stored 100001
INVOICE is stored L100001-000
here's the code I've been using to date to do a quicky equi-join. Should I just temptable this bitch?
i.INVOICE like ("%" + CONVERT(varchar(20), lol.invoice_num) + "%")
Deebaser on
0
Posts
Honestly, I've had nothing but trouble with Access in scientific contexts. It refuses to sync with stuff, packages to interface with other apps are usaully a pain to work with and the support is rather sad (comapred to OS stuff).
Also, where are you defining this join? That might help out.
you are correct, INVOICE is a varchar and invoice_num is an int. (Why the devs made INVOICE a varchar is a mystery lost to time). There is nothing I can use to map the numbers to the varchar straight out.
Right now Im performing the join in the WHERE of a simple select.
I would, but the SQL client that our company uses is pretty gimp. The data Im trying to pull from is on different servers and ODBC through Access would make my life easier.
So have a query that is named "CLEAN_INVOICE" that is just a selects the necessary fields from that table and does a convert from varchar to number. Then use that query like a view for all future queries.