51

(6 replies, posted in Setup)

Thank you kindly for the response.

If you HAVE received the goods, you just owe the guy money and you just book the entry using existing accounts.   

dr Purchases Received (inventory or Supplies)
   cr Accounts Payable
-to recognize goods received but not yet paid for.

If you HAVE received the goods but haven't credited your supplier yet (I suppose to examine the receipt first) then you could

dr Purchases Received (inventory or Supplies)
   cr Clearing Account
-to recognize goods received but not yet paid for.

and then...

dr Clearing Account
   cr A/C Payable
to reflect a liability for goods received.

One could certainly do this, but this isn't really "standard" for most business' that I'm aware of and making this a Standard COA account is not recommended.  Simplicity is always better.  I would argue that ERP (like FA) systems especially don't need this, as Purchase Orders Outstanding are tracked.  If they aren't using a PO to place their order, then they aren't using the tools they have properly.  Right? 

Perhaps I'm not understanding your argument fully.  If so, I apologize.

This kind of reminds me of a Story my old accounting professor told us.  He went into a company and the bookkeeper had a "CM" account.  He inquired, "What is that CM account for?  The bookkeeper replied, "Well, we have a cat."   My professor said, "so?".  The bookkeeper said, "Well, we debit that for the cat meat we purchased. Cat Meat, CM."  His lesson to us.  Don't ever set up a Cat Meat account.  Use miscellaneous.

52

(57 replies, posted in Installation)

OK, went through the install again.  I'm doing this on a local host running POP OS, a linux distro I really like.  After the install I got something that said you must change session.inc to say secure = to false, so I figured what the heck, I'm only running this locally so I did it.  I'm not sure this affected the outcome, but I'm very happy to say that the HRM module worked!  I'm able to add employees and update them as well.  I may try this again in a different environment, but at least it's working fine now.  Thank you J. for your input.  I'm a local (read one man shop) CPA here in the States, and I hope to continue to use this product and offer any suggestions that I think might be helpful.  THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU!

itronics wrote:

. Regarding problems with FrontHrm module, I have updated repo content to the last version available on Nostrinos github page.
Please install module via 'Install/activate Extensions' page, set access to the module on 'Access setup' page, then log out and log in again.
The module works as expected. Please send any bugfixes or feature request related to this module stright to Nostrinos via his github bugtracker. We do not maintain the module (beyond FA repo integration), so all thanks and/or claims please send to the author.

J.

53

(6 replies, posted in Setup)

I'm not certain what we mean by a "Clearing Account".  I suppose it's some kind of a suspense account.  It's not a common COA account.
I would say if someone needs it, let them add it in.  A lot of accounting software takes the approach that less is more.  If ONE person needs that account, that means that the other NINE people won't use it.  Default accounts should, in my opinion, be accounts every business will use.  A clearning account sounds like it's business specific, or a suspense account like I said.  In any event, I personally would not encourage you to change anything about the FA COA.  I really like them as they are.  My 2 cents.

boxygen wrote:

In this function gl_account_in_company_defaults
please add one more line

OR name='grn_clearing_act'

(UPDATE 012823 - PLEASE SEE MY LATEST REPLY - IF INTERESTED - CONCERNING THE HRM MODULE.  I WAS ABLE TO GET IT WORKING)

I am delighted to get your response.  OK, I will try it again.  If it can "add employees" I will be totally surprised, and I will let you know that it worked.  If it doesn't work then - - given that it works for you -- I would have to say it's some kind of configuration setting that is "setting" many of us off.  I've had it throw php errors before but the error messages are not really helpful.   

Insofar as the size of the fonts, I'm happy to hear you're doing a minor face lift.  But it's not the fonts I was referring to.  I agree also that it should not necessarily be designed with the "mobile phone" in mind.  (After all, who would actually do accounting on their phone?  Perhaps looks at a customer inquiry, but that's about it.)   It's more about the way it lives on screen real estate.  Seems it could be spread out more, or made bigger in general.  Not sure.  Perhaps some css improvements?  In any event, I'm not hung up on the looks of it.  I'm more about the functionality. FA is a very impressive application.  Which is one of the reasons I keep coming back to it. 

Thanks again for your response. I will try it 'again' - even though I said I was done with it ;-| and report back what I find.

Thanks,

MacKenzie

55

(3 replies, posted in Wish List)

Please, let's try to keep the discussions somewhat relevant.  Seeing posts up there from 2012, 2016, etc., is, hmm, what's a polite way to say this, it's let's just say it makes us all look like we're not candidates for mensa by any stretch of the imagination.  Any posts older than 24 months needs to be deleted, or at least archived with notice that users can search the HISTORIC posts of the days of yesteryear.

56

(57 replies, posted in Installation)

Thanks for the reply.

57

(57 replies, posted in Installation)

The HRM module still does not work properly.  It still can not even "add" an employee.  Without the ability to "add" an employee, the module has no utility whatsoever.  I've seen complaints concerning this for months.  Many many "would be" users have voiced similar criticisms.   Thanks.

notrinos wrote:

I have created a minor repository at repo.notrinos.com
Someone who facing the same problem can temporary switch to repo.notrinos.com
Do the following:

- Open version.php then at line 23 replace repo.frontaccounting.eu with repo.notrinos.com
- Replace FA.pem with the attached herewith or Open FA.pem then replace it's content with the below:

-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA71QcW3pUnzkE31fCH0hN
+3to2pi3ILfshzLYTl2O1HDb5YjFEG4KbwlXfc533F7WMeyWg/wBPldV1ti05/uf
5wMnqrzeZG5Br/XjSDvoYS0Be7ktya9m4OWeG0SVjGKjxkqqPJZR1U1wk5cGu4QS
8MTpTf14WhP1mGGMgSH2V5W8mlr3qf4nZ6gZ7eqdY+HOwScbL/myagoWaLnrNsar
D52Ysg4O1YOM46NLu/EmpLOKPWT/77MMU2aw793wSxltJksf9gUa2JaZq0bd/oP1
3hxiBRGj4mGALON8rpY1ULAjtH1VJmL2tgH5lmW5ubTO+GolHd5D4QE6LKOHfI20
IQIDAQAB
-----END PUBLIC KEY-----

Remember backup the two above files for later use when you want to go back with the original repo.

I'm a long time FA user and I really like the product.  I personally think it needs a major face lift (very small font/footprint) and some serious modules to keep it current, but it's a great product and can do lots of things your average QB or Xero software can NOT do.  But it really needs an "employees" tab and basic stuff like that.  Which brings me to the HRM module.

The HRM module.  Where do I begin?  Hmm. I don't mean to sound ungrateful.  I'm sure a lot of work went into this module.  But it simply doesn't work properly.  I've tried it on several platforms, and I've used several code bases recommended, but it just doesn't work properly.  FA probably needs to set up a "beta Extensions" test repository where stuff like HRMs can be uploaded, explored, fixed, changed, tested, etc.  Once it passes the test, then the governors could agree it's ready.  Just about every other module I've tried works, and works pretty well.  The developers are to be commended for volunteering their time and resources for those contributions.  But something like the HRM module, while perhaps good on some level, really doesn't belong in the repository.  It weakens the FA product (which I find to be generally a really good product).  Again, I don't mean to sound ungrateful.  And yes, I understand this is "open source" code.  Go back and look at all the comments.  There are a "ton" of comments about this module not working.  And to tell someone "oh, you need to download it from here" or "this has been fixed" or "you didn't install it correctly" is just preposterous.  There is absolutely no way this module is ready for prime time and to list it with other 'real' extension is misleading at best.    Please take this in the spirit it is intended.  Not to dump on any developer or group of developers who I'm sure are making a living doing something besides FA. Thanks.

Installed the latest version of HRM.  It can not be accessed.  https://imgflip.com/i/76ylq9

:-)  Yes, I've used it.  I've installed it.  That specific module from Notrinos.  No joy.  It fails to add employees in the HRM module, and once I actually put employees "manually" in the db, the module can not delete them.  Any other suggestions would be appreciated.  Thx.

Note:  This issue is not restricted to running it locally (I have an instance running) or running it remotely on a web server.  I'm not sure if it occurs in Windows and I don't care.  I don't use Windows OS.  Ever.

61

(7 replies, posted in Setup)

Deleting a customer in what module?  HRM?  I can't get that to delete an employee either.  But that's ok, it won't let me add an employee either. LOL.

The HRM module is a much needed extension that will help elevate FA.  Thanks for everyone's hard work on this much needed module.

From reading the forum, it has had numerous corrections/changes/modifications and it looks like they are spread out over several modules/programs/lines of code.  Have any of the change been consolidated in "one place" so we can just install it and have it work?  Thank you in advance.

Linux

I'm getting errors trying to write to the database so I'm unable to update the employees in the HRM module. Any help would be appreciated.

mysqli_connect(): Headers and client library minor version mismatch. Headers:100508 Library:100236 in file: /home/myweb/public_html/acctg2/includes/db/connect_db_mysqli.inc at line 33
/home/myweb/public_html/acctg2/includes/db/connect_db_mysqli.inc:33:    mysqli_connect('localhost','myweb_fron201','36(b1m2S!p','','3306')
/home/myweb/public_html/acctg2/includes/session.inc:579:    set_global_connection()
/home/myweb/public_html/acctg2/modules/FrontHrm/manage/employee.php:16:    include_once('/home/myweb/public_html/acctg2/includes/session.inc')


trigger_error('DATABASE ERROR : Could not write employee data
error code : 1366
 
error message : Incorrect integer value: '' for column `myweb_fron201`.`0_employee`.`emp_id` at row 1

I've done some research on this issue in the FrontAccounting forum.  I noticed that this error code in relation to NOT being able to update a database has been in existence since 2008.