Search results for query: *

Disclaimer : I don't know oracle However, it looks to me like your test procedure doesn't return anything, merely sets the varable a. try: create or replace PROCEDURE TEST BEGIN SELECT empno from emp WHERE sal=1950; END; this should return a recordset containing field empno.

try: if not qVar.executeQBE("test.dbf") then errorshow() endif and see if you get an errormessage Richie

I've had the same message from mssql when running a Stored Proc. The solution was to edit the procedure and remove all output except the final table. Use SET NOCOUNT ON to get rid of all "xxx rows affected" lines and remove any print statements in the Procedure. HTH, Richie

I haven't tested this but ,have you tried vbCrLF? Richie

I don't know if this is causing to your problem, but I'd avoid using "Type" as a field name. This is a keyword and might be confusing the issue. Richie "Supreme executive power derives from a mandate from the masses, not from some farsical aquatic ceremony." - also Dennis

You need parens around the field name. Also, don't you need the wildcard % ? strTest = "SELECT MAX(PurchaseOrderID) FROM PurchaseOrder WHERE PurchaseOrderID LIKE '" & _ left(strPONum,5) & "%'" HTH, Richie

On second thoughts scratch that last reply. You don't need the thickness field in the parts table at all. Why repeat the data if the plateID will give you the part thickness anyway? If you need to find out the thickness of the part you should be able to get it from the plate table linking by...

If I understand your problem correctly, you could try linking the tables with both (ID and thickness) fields. You may have to restructure one or both tables to make thickness part of the primary key. This way items in the parts table must have the same thickness as the plate. Try it on a copy to...

There are several ways of doing this but the simplest is to edit the report and add a text object (called eg.daterange) where ever you want it. Save but don't deliver the report. In your pushbutton r.load("reportname.rsl", winstylehidden) r.daterange.text = "From " +...

Have you looked at INSERT queries? This will place the results of your query into a predefined table of your own design. Assuming the fields fit. Richie

This is because you have data that is not conforming to the nnnXnnn standard, probably blank. Check the size or the array before trying to reference it oldNums.breakApart(arDims,"X") if arDims.size() = 2 then tcDims."Width" = arDims[1] tcDims."Thick" =...

I don't use this myself but, if you feel like playing around with it the form tutil32.fdl is what the menu calls. So to rebuild the answer.db with minimal user interface: var f form endvar f.open("c:\\program files\\borland\\paradox\\tutil32.fdl", winstylehidden) f.fldTable =...

I just noticed from an earlier post of yours that you probably don't have the filter variable. In this case use getgenfilter in the form. var r report criteria dynarray[] anytype endvar ; capture the filter criteria -tableframeobject-.getgenfilter(criteria) ; the rest is the same...

Another simple way is to apply the exact same filter to the report. eg. var r report endvar ;assuming you've already set up filter in criteria ; load report hidden in design mode r.load(-reportname-, winstylehidden) ; note: report must be .rsl not delivered r. -tableframename-...

mtstad, FYI the most common reasons is see for problems in filtering or querying for date ranges are 1. Get No results : a. There really are no matches (most common reason) b. Mixing up >,< eg. &quot;<12/31/2001, >2/1/2002&quot; 2. Get Everything in table: using OR instead of...

What kind of trouble are you having? Seeing nothing, seeing everything? This kind of code should work: daCrit[&quot;Date&quot;] = &quot;>12/31/2000, <2/1/2001&quot; tc.setgenfilter(daCrit) If this is what your date field filter looks like then you may have a problem in another field. Post some...

You could use the master table in the form and apply a filter to it. var f form daCriteria dynarray[] anytype endvar contnum = 0 contnum.view(&quot;Enter A Contract Number:-&quot;) strnum = 0 strnum.view(&quot;Enter A Structure Number:-&quot;) daCriteria[&quot;Cont#&quot;] = contnum...

Personally I've never felt the need to go beyond 7. There just wasn't anything compelling (to me) added in later versions. I just keep the BDE up to date. ros

Another date to try is 12/31/2001. Year subraction will give an age of 1 to a newborn less than 2 weeks old. Correct age of 0 will be given by the suggested algorithm. ros

>>That is, if you enter 02 as year, Podx treat it as 1902, not 2002. This is not the case in paradox 32bit. Your examples disprove your point not prove it. if you enter 1/1/61 paradox treats it as 1/1/2061, CURRENT century as I stated. The calculation is correct 2002 - 2061 DOES EQUAL -59...