Re: SQL Fustrations

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Brian Shafer (BrianShafer_at_discussions.microsoft.com)
Date: 06/10/04 

Date: Thu, 10 Jun 2004 14:18:01 -0700

Ok Jeff,
I can't attach files from the MS communities(Web), so I'll do it at home...
How do you want me to do it? Strip the DB's down and send those, or just give you a document which names the fields and data types? and then send you the project code for my vb app?
and would you like those zipped up?
 Just let me know,
Brian

"Jeff Johnson [MVP: VB]" wrote:

>
> "Brian Shafer" <BrianShafer@discussions.microsoft.com> wrote in message
> news:18B576FD-688B-496E-8919-288F325385D2@microsoft.com...
>
> > A mixture of number and text... this one produces an error in vb, but not
> access....
> > INSERT INTO [History-Roll ground] ([Grinder no], [Start date/time],
> [Rolling mill], [Roll type], [Roll material], [Roll Nb], [Roll code],
> [Program code], [Profile code], [Profile height], [Dress code], [Dress
> height], [Diam before mid], [End date/time], [Regrind status], [Present diam
> max], [Present diam min], [Present diam head], [Present diam mid], [Present
> diam tail], Taper, Profile, Roundness, Runout, Crack, [C Position], [C
> Angle], Bruise, [B Position], [B Angle], MaxStructure, MinStructure,
> Ultrasound, [U Position], [U Angle], [Wheel dia start], [Wheel dia end],
> [Roughness head], [Roughness mid], [Roughness tail], [Hardness head],
> [Hardness mid], [Hardness tail], Remarks, [Validate/Discard], [Operator
> code], [Wheel type], [Wheel no], [Last use mid dia], IntTime, WeightRemoved)
> VALUES( '3', #6/5/2004 19:07:35#, '1', '1', 'NA', '10418', 'F1-F3', '1122
> F1-3', '2001', '-0.00039', 'test', '0', '30.31012', #6/6/2004 00:09:25#,
> '3', 30.29838, 30.29739, 30.29746, 30.29782, 30.29838, 0.00034, 0.00097,
> 0.00014,
> > 0.00022, 8, 21.65346, 1, 16, 21.65346, 1, 0, 0, 0, 0, 0, 26.2767,
> 25.95931, 0, 0, 0, 0, 0, 0, 'NA', 'V', 'operator', 'National41C3622M7-BD',
> 1, 0, 6249, 11.57736)
>
> I'll try hard not to make a comment like "shoot whoever chose field names
> with spaces" (oops, I just made one!) and ask this: is [Diam before mid]
> numeric? Because you have the value in apostrophes in the VALUES clause
> ('30.31012'). I doubt that would cause the error you are getting, but it's
> worth mentioning.
>
> Beyond that we REALLY NEED TO SEE THE CODE, not just the SQL statement.
> Given that the task is already past due, you'd be doing yourself a favor to
> give us all the info we need so that it doesn't drag out further as we ask
> you to supply more.
>
>
>