Search results for query: *

I read that you had not run any depreciation before you changed it. Did you change the accounts on the asset itself or just the class? Changes to class data does not 'roll down' to existing assets. Did the change ever take effect? Kind regards, Leslie

no Kind regards, Leslie

If you can log in as 'sa', you have the keys to the kingdom. Remember who 'sa' is, 'sa' is the SQL administrator. Sa is managed using SQL, not GP. That's why you can't change sa's password in GP. Use the following SQL statement to remove the gp system password: UPDATE DYNAMICS..SY02400 SET...

Another option is to just delete them from the customer master and leave the transactions in place. It's the same thing the system does when you are allowed to delete a 'temporary' vendor. If you ever need to hook up the transactions with the now deleted customer, just re-enter the customer ID...

The 64-bit vs 32-bit isn't the problem. I'm not sure what is, but you might just try copying the .dic and .exe files from the 32 bit to the 64 bit. The error message is unhappy about build numbers, not 'bits'. slantsix Kind regards, Leslie

Wow, 900 orders, I would not have wanted to do that job, hurray for the person who did it! Leslie

You cannot depreciate an inventory item, only a fixed asset. If you need to continue the depreciation, why are you putting it into inventory?

To which event have you attached this script?

Those tables are not as cryptic as you may think. There is a definite naming convention that anyone working with the tables should know. The prefix refers to the module GL, SOP, POP, et cetera. The rest of the numbers follow this scheme: 00000 Master Files 10000 Work Files 20000 Open Files...

I also wanted to mention that there are 7 aging buckets in AR, make sure you only are using 4 of them or you might not capture all of your outstanding receivables.

Are you using any VB Script or making an ADO connection?

It sounds like you are doing it right, 1. Put the customer number from the RM Cust MSTR in the Customer Footer 2. Get rid of all report sections except the Customer Footer and the Report Header 3. Put the Legends in the Report Header. 4. Get rid of all other fields and lines except Customer...

I guess it depends on what you mean by 'incompatible'. There are some features in GP2010 (and gp 10 for that matter) that do not work with native 2003. You have to at least have the 2007 viewer installed. Suspects of incompatibility include: Office Data Connections (.odc) The new reporting...

These are Orders and not invoices? I know you said Void, but I'll put a couple of options one out there. 1. Using SQL, put all of the Orders into a single batch (simply change the BACHNUMB field in SOP10100). Delete the single batch. You will not be able to delete any documents that have been...